[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20140722.195222.775371949777233094.davem@davemloft.net>
Date: Tue, 22 Jul 2014 19:52:22 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: ezequiel.garcia@...e-electrons.com
Cc: thomas.petazzoni@...e-electrons.com, netdev@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, jason@...edaemon.net,
mw@...ihalf.com, gregory.clement@...e-electrons.com,
tawfik@...vell.com, alior@...vell.com
Subject: Re: [PATCH 0/6] net: mvpp2: Assorted fixes
From: David Miller <davem@...emloft.net>
Date: Tue, 22 Jul 2014 17:41:53 -0700 (PDT)
> From: Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>
> Date: Tue, 22 Jul 2014 20:20:04 -0300
>
>> On 23 Jul 12:29 AM, Thomas Petazzoni wrote:
>>> On Tue, 22 Jul 2014 13:16:39 -0700 (PDT), David Miller wrote:
>>>
>>> > >> This series does not apply to the 'net' tree at all, please respin
>>> > >> and resubmit.
>>> > >
>>> > > This series applies on net-next.
>>> > >
>>> > > Sorry for not mentioning it,
>>> >
>>> > They are bonafide bug fixes, therefore should be targetted at 'net'.
>>>
>>> Except that I believe they are fixes for a driver which itself is in
>>> net-next, i.e scheduled for 3.17.
>>>
>>
>> That's right. These are fixes for the new mvpp2 driver, which is only
>> in net-next.
>
> Ok, I queued them back up, thanks for the clarification.
I've applied the 4 driver patches to net-next. But, since the ARM
device tree file changes did not go into net-next, I can't apply the
last two patches to my tree. You'll need to sort that out yourself.
It's a bit unfortunate that things are now out of sync like this, but
that's what you asked me to do.
--
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