[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20180728.221411.871884033416188094.davem@davemloft.net>
Date: Sat, 28 Jul 2018 22:14:11 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: gregory.clement@...tlin.com
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
thomas.petazzoni@...tlin.com, linux-arm-kernel@...ts.infradead.org,
jason@...edaemon.net, andrew@...n.ch,
sebastian.hesselbarth@...il.com, yelena@...vell.com,
nadavh@...vell.com, mw@...ihalf.com, dima@...vell.com,
antoine.tenart@...tlin.com, miquel.raynal@...tlin.com,
maxime.chevallier@...tlin.com
Subject: Re: [PATCH net-next v3 0/8] A fix and a few improvements on mvneta
From: Gregory CLEMENT <gregory.clement@...tlin.com>
Date: Tue, 24 Jul 2018 15:16:52 +0200
> Hi David,
>
> On mer., juil. 18 2018, Gregory CLEMENT <gregory.clement@...tlin.com> wrote:
>
>> Hello,
>>
>> This series brings some improvements for the mvneta driver and also
>> adds a fix.
>>
>> Compared to the v2, the main change is another patch fixing a bug
>> in mtu_change.
>>
>
> I saw in patchwork, the status was "Accepted" (for example the 1st patch
> [1]). However the series is not in your git branches and usually you
> also answered to the series to inform that you have applied it. So I
> would like to know what is the status of the series.
This series should now really be in net-next.
Sorry about that!
Powered by blists - more mailing lists