[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANhJrGN+PdDGDnZaido8Tizc4X4su6E=z-xWJAY4NbNrXG22wA@mail.gmail.com>
Date: Wed, 9 Nov 2011 11:57:13 +0200
From: Maz The Northener <mazziesaccount@...il.com>
To: David Miller <davem@...emloft.net>,
Matti Vaittinen <matti.vaittinen@....com>
Cc: netdev@...r.kernel.org
Subject: Re: patch "workflow" - what deferred state means?
On Mon, Nov 7, 2011 at 10:19 PM, David Miller <davem@...emloft.net> wrote:
> From: Maz The Northener <mazziesaccount@...il.com>
> Date: Mon, 7 Nov 2011 22:08:00 +0200
>
>> I was talking about http://patchwork.ozlabs.org/patch/123407/ and
>> patchwork.ozlabs.org/patch/123406/
>
> This kind of work should be resubmitted when net-next opens back up.
>
I assume now would be correct time, right? If I am correct, net-next
is open now due to linux 3.2-rc1 (If I am wrong, please tell me how I
know when net-next is opened).
So I should resubmit the patches. I just fetched snapshot from
net-next.git at kernel.org, and tried applying the patches. Applying
succeeded but with offset. So should I redo patches on top of some
other kernel, and if so, which one?
-Matti
--
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