[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.00.1001042300160.2277@pobox.suse.cz>
Date: Mon, 4 Jan 2010 23:00:40 +0100 (CET)
From: Jiri Kosina <jkosina@...e.cz>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: James Bottomley <James.Bottomley@...e.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Stefani Seibold <stefani@...bold.net>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-scsi <linux-scsi@...r.kernel.org>,
Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [PATCH] libsrp: fix compile failure
On Mon, 4 Jan 2010, Andrew Morton wrote:
> > Yes, it indeed is that way -- Andew pulls whole linux-next as one of the
> > patches into -mm series.
> >
> > To make linux-next really working the way it is intended to work we need
> > to have -mm part of it, as it is used as a last point for a non-trivial
> > amount of patches before they enter Linus' tree.
> >
> > Andrew, why do we have the current setup, and not the other way around?
>
> Because I suck. I haven't yet got around to feeding -mm into
> linux-next. It's a bit tricky, because -mm is based on linux-next.
> Probably we'll address this by adding a "linux-next before the mm bits"
> marker to linux-next.
Yup. That should work and would be really helpful.
--
Jiri Kosina
SUSE Labs, Novell Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists