[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d76b854c-5f6d-27b6-d40e-e3c0404b5695@huawei.com>
Date: Thu, 17 Oct 2019 11:27:09 +0800
From: tanhuazhong <tanhuazhong@...wei.com>
To: David Miller <davem@...emloft.net>, <jakub.kicinski@...ronome.com>
CC: <netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<salil.mehta@...wei.com>, <yisen.zhuang@...wei.com>,
<linuxarm@...wei.com>
Subject: Re: [PATCH net-next 00/12] net: hns3: add some bugfixes and
optimizations
On 2019/10/17 1:50, David Miller wrote:
> From: Jakub Kicinski <jakub.kicinski@...ronome.com>
> Date: Wed, 16 Oct 2019 10:19:43 -0700
>
>> On Wed, 16 Oct 2019 15:16:59 +0800, Huazhong Tan wrote:
>>> This patch-set includes some bugfixes and code optimizations
>>> for the HNS3 ethernet controller driver.
>>
>> The code LGTM, mostly, but it certainly seems like patches 2, 3 and 4
>> should be a separate series targeting the net tree :(
>
> Agreed, there are legitimate bug fixes.
>
> I have to say that I see this happening a lot, hns3 bug fixes targetting
> net-next in a larger series of cleanups and other kinds of changes.
>
> Please handle this delegation properly. Send bug fixes as a series targetting
> 'net', and send everything else targetting 'net-next'.
>
Hi, David & Jakub.
BTW, patch01 is a cleanup which is needed by patch02,
if patch01 targetting 'net-next', patch02 targetting 'net',
there will be a gap again. How should I deal with this case?
MBR.
Huazhong.
> .
>
Powered by blists - more mailing lists