On Mon, Jul 9, 2012 at 10:44 PM, Joe Perches <j...@perches.com> wrote:
>> > That single patch doesn't apply cleanly to Linus' >> > 8c84bf4166a4698296342841a549bbee03860ac0 >> > >> > What else is necessary? >> > >> > Your tree seems to have a collection of random patches. >> > >> > It might be useful to clone Linus' tree and produce a >> > branch with all the necessary printk patches in it so >> > someone else could pull it. I just worked on top of Greg's tree with the pending stuff for 3.5. >> They should all now be in my driver-core-next branch that will show up >> in the next linux-next release, so having a separate tree isn't >> necessary. > > I don't think so. > > There are real defects in the existing code. > > These are patches that are necessary _now_. > not for a -next 3.6 future. Wrong conclusion. They are not in the 3.6 branch, but still go into -next: http://git.kernel.org/?p=linux/kernel/git/gregkh/driver-core.git;a=shortlog;h=refs/heads/driver-core-linus Kay -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
