On Mon, 2008-07-14 at 21:09 +0200, Michael Buesch wrote:Right, this is where spi-gpio is, please disregard my question in the mmc-spi-gpio thing thread, it was domestic blindness after all :-) Looks good overall. I'm not sure that it need pretend to be hotpluggable though (i.e. the board info can be hardwired so there's no need for the board setup callback). I guess this is to integrate with your "dynamically create an mmc over spi over gpio" thinggy in the other thread. As I said there, I'd prefer that this platform device is treated like other platform devices and any dynamicness be introduced at in a more generic way. What problem are you solving (or whole in board support are you plugging) in this dynamic plugging of MMCs? Thanks, --Ben. --
| Jens Axboe | Re: [BUG] New Kernel Bugs |
| Faik Uygur | Re: Linux 2.6.21-rc1 |
| Ingo Molnar | [patch 02/13] syslets: add syslet.h include file, user API/ABI definitions |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
git: | |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | Re: Data corruption issue with splice() on 2.6.27.10 |
| Steven Rostedt | Re: -rt scheduling: wakeup bug? |
