Hi all, I have a hard time maintaining the i2c subsystem alone. New drivers and, more importantly, subsystem evolutions are submitted much faster than I can review and merge them. I am hearing complaints about this. It has been lasting for a while now and it doesn't seem like the situation is going to improve. Thus, I think it would be better if someone was co-maintaining the i2c subsystem with me. So, if anyone is interested in co-maintaining the i2c subsystem with me, please let me know. The ideal candidate would come from the embedded world, as I have absolutely no experience with this myself and most of the new drivers are for embedded devices, and should have contributed to the kernel in a significant way already. Thanks, -- Jean Delvare --
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Linus Torvalds | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| David Newall | Re: Slow DOWN, please!!! |
| Ian Campbell | Re: [PATCH] x86: Construct 32 bit boot time page tables in native format. |
| Matthias Scheler | Re: HEADS UP: timecounters (branch simonb-timecounters) merged into -current |
| Greg Troxel | Re: Interface to change NFS exports |
| Thor Lancelot Simon | metadata cache and memory fragmentation |
| YAMAMOTO Takashi | amap memory allocation |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| David Miller | [GIT]: Networking |
| Dushan Tcholich | Re: ksoftirqd high cpu load on kernels 2.6.24 to 2.6.27-rc1-mm1 |
