Re: x86: fix a couple of sparse warnings

From: Sam Ravnborg
Date: Mon Apr 28 2008 - 15:13:38 EST


On Mon, Apr 28, 2008 at 09:56:08PM +0300, Adrian Bunk wrote:
> On Mon, Apr 28, 2008 at 05:01:56PM +0200, Ingo Molnar wrote:
> >
> > * Adrian Bunk <bunk@xxxxxxxxxx> wrote:
> >
> > > On Mon, Apr 28, 2008 at 05:43:25PM +0400, Dmitri Vorobiev wrote:
> > > > 2008/4/28 Adrian Bunk <bunk@xxxxxxxxxx>:
> > > > >
> > > > > /me wonders what was wrong with http://lkml.org/lkml/2008/4/23/131
> > > > > that contains a superset of the first patch
> > > > > (and got no response at all)
> > > >
> > > > Adrian, I am sorry for duplicating your work. The clash wasn't
> > > > intentional: I did not notice your earlier patch in the high traffic
> > > > of this mailing list.
> > >
> > > No problem, and I'm actually more interested why my patch got lost.
> >
> > It's simple: in this case i had two patches in my backlog, one from a
> > new person and one from a frequent contributor - doing the very same
> > change. I preferred the newbie's patch, to encourage Dmitri to keep
> > contributing to Linux and to help him learn from the experience of
> > working with various Linux maintainers.
> >...
>
> Every maintainer except you will teach the newbie where to find the
> current tree to avoid duplicating work...
I have seen Ingo referring to his README file countless number of
times which describes where to locate the x86.git tree and
how to pull it. So has you.

Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/