[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20120511142932.af7851bd.akpm@linux-foundation.org>
Date: Fri, 11 May 2012 14:29:32 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: David Miller <davem@...emloft.net>
Cc: mgorman@...e.de, linux-mm@...ck.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, neilb@...e.de,
a.p.zijlstra@...llo.nl, michaelc@...wisc.edu, emunson@...bm.net
Subject: Re: [PATCH 00/17] Swap-over-NBD without deadlocking V10
On Fri, 11 May 2012 17:23:39 -0400 (EDT)
David Miller <davem@...emloft.net> wrote:
> From: Mel Gorman <mgorman@...e.de>
> Date: Fri, 11 May 2012 16:45:40 +0100
>
> > From my point of view, the ideal would be that all the patches go
> > through akpm's tree or yours but that probably will cause merge
> > difficulties.
> >
> > Any recommendations?
>
> I know there will be networking side conflicts very soon, it's not a
> matter of 'if' but 'when'.
>
> But the trick is that I bet the 'mm' and 'slab' folks are in a similar
> situation.
>
> In any event I'm more than happy to take it all in my tree.
I guess either is OK. The main thing is to get it all reviewed and
tested, after all.
I can take all the patches once it's all lined up and everyone is
happy. If the net bits later take significant damage then I can squirt them
at you once the core MM bits are merged. That would give you a few
days to check them over and get them into Linus. If that's a problem,
we can hold the net bits over for a cycle.
That's all assuming that the core MM parts are mergeable without the
net parts being merged. I trust that's the case!
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists