Re: [PATCH v3 2/4] spi: split up spi_new_device() to allow two stage registration.

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: David Brownell
Date: Friday, July 25, 2008 - 12:00 pm

On Friday 25 July 2008, Grant Likely wrote:

Mention an example please ... you have dev->archdata in mind, yes?



Comment needs fixing:  *TWO* new functions, spi_device_release() was
not needed ...



Strike "an".  :)


Given the comment fixes noted above and below:


Acked-by: David Brownell <dbrownell@users.sourceforge.net>

Thanks.




"a" spi_device


Strike "an".



Nit;  "cs%d >= max %d" ... no need to carry this minor bug forward.



Hmm, I just noticed this *pre-existing* bug:  if there's already
a device with this chipselect (so the device_add will fail, later),
its configuration will be trashed here.  That's not a reason to NAK
this patch.  (I think the fix would be as simple as calling setup
in spi_drv_probe, and making sure that's always called even if for
some odd reason the driver doesn't have its own probe routine.  If
you want to fix that, great ... otherwise I'll try to get it done
before 2.6.27 finishes.)



to, for, sex, ate ... voudou will appreciate!!  ;)

Make that "to use" a two stage registration "sequence".


"... before it is registered, but requires that caller to initialize fields that
would otherwise be defined using the board info."




--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH v3 0/4 REPOST] OF infrastructure for SPI devices, Grant Likely, (Fri Jul 25, 12:33 am)
[PATCH v3 3/4] spi: Add OF binding support for SPI busses, Grant Likely, (Fri Jul 25, 12:33 am)
Re: [PATCH v3 2/4] spi: split up spi_new_device() to allow ..., David Brownell, (Fri Jul 25, 12:00 pm)