On Mon, Jul 09, 2012 at 01:56:31PM -0700, Greg Kroah-Hartman 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.
> > >
> > > 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.
>
> Oops, sorry, I ment to type, "driver-core-linus" above.
Can you get this to Linus asap please ? I just had an oops that scrolled
off the screen because the Code: line suffers the same problem.
Thankfully serial console caught most of it, but I had to hand-edit
a lot of crap just to make it readable again.
Dave
--
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/
