[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100624205059.a28756b0.akpm@linux-foundation.org>
Date: Thu, 24 Jun 2010 20:50:59 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: David Miller <davem@...emloft.net>
Cc: herbert@...dor.hengli.com.au, mst@...hat.com, frzhang@...hat.com,
netdev@...r.kernel.org, amwang@...hat.com, shemminger@...tta.com,
mpm@...enic.com, paulmck@...ux.vnet.ibm.com,
a.p.zijlstra@...llo.nl, mingo@...e.hu
Subject: Re: [PATCH 6/8] netpoll: Allow netpoll_setup/cleanup recursion
On Thu, 24 Jun 2010 20:30:06 -0700 (PDT) David Miller <davem@...emloft.net> wrote:
> From: Andrew Morton <akpm@...ux-foundation.org>
> Date: Thu, 24 Jun 2010 18:21:23 -0700
>
> > Dave, the fixup should be folded into the original patch please -
> > otherwise we'll have a machine-hangs-up bisection hole which spans two
> > weeks work of commits.
>
> I'm not unwrapping my tree that far back, and there's already been
> a dependent tree pull or two which depend upon the tree past that
> commit, one of it was a rather large wireless merge.
>
> It's going to screw over too many people.
>
> We'll just merge the bug fix in, and be done with it.
Sigh. That really sucks.
What happens if you want to actually *drop* a patch from net-next?
Surely that happens?
--
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