[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d8e6fde9-6089-bf71-438e-5263758f3474@huawei.com>
Date: Fri, 12 Jan 2018 11:26:53 +0800
From: "lipeng (Y)" <lipeng321@...wei.com>
To: David Miller <davem@...emloft.net>
CC: <netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linuxarm@...wei.com>, <salil.mehta@...wei.com>
Subject: Re: [PATCH net-next 00/11] add some new features and fix some bugs
On 2018/1/12 1:07, David Miller wrote:
> From: Peng Li <lipeng321@...wei.com>
> Date: Thu, 11 Jan 2018 19:45:55 +0800
>
>> This patchset adds some new features and fixes some bugs:
>> [patch 1/11] adds ethtool_ops.get_channels support for VF.
>> [patch 2/11] removes TSO config command from VF driver.
>> [patch 3/11] adds ethtool_ops.get_coalesce support to PF.
>> [patch 4/11] adds ethtool_ops.set_coalesce support to PF.
>> [patch 5/11 - 11/11] do some code improvements and fix some bugs.
> Can you please write a real commit message in your header postings
> please?
>
> Don't just copy the subject lines from the patches, and add one
> sentence with a brief description.
>
> Really write real paragraphs describing what the patch series
> is doing, how it is doing it, and why it is doing it that
> way.
>
> A real explanation that tells the reader what exactly to
> expect when they review the patches themselves.
Thanks for your advice.
A detail explanation is better for review, I will write
the "real explanation" in V2 patch-set.
Peng Li
> Thank you.
>
> .
Powered by blists - more mailing lists