From: David Miller <davem@davemloft.net>
To: tanhuazhong@huawei.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
salil.mehta@huawei.com, yisen.zhuang@huawei.com,
linuxarm@huawei.com, shenjian15@huawei.com
Subject: Re: [PATCH net-next 01/12] net: hns3: fix VLAN initialization to be compatible with port base insert VLAN
Date: Thu, 11 Apr 2019 21:26:41 -0700 (PDT) [thread overview]
Message-ID: <20190411.212641.809336343201829564.davem@davemloft.net> (raw)
In-Reply-To: <0a650f2c-7988-5ff3-68ad-909005fc50c9@huawei.com>
From: tanhuazhong <tanhuazhong@huawei.com>
Date: Fri, 12 Apr 2019 10:30:38 +0800
>
>
> On 2019/4/12 2:20, David Miller wrote:
>> From: Huazhong Tan <tanhuazhong@huawei.com>
>> Date: Thu, 11 Apr 2019 20:25:20 +0800
>>
>>> From: Jian Shen <shenjian15@huawei.com>
>>>
>>> This patch fixes VLAN initialization, in order to be compatible
>>> with VLAN inserted base on port.
>> This doesn't mean anything to me.
>> Why was normal VLAN initialization different, and how is the behavior
>> of VLAN's configured when inserted based upon port different and why
>> is it better?
>> You have to improve your commit log messages so that someone not
>> intimately familiar with your driver and code can understand what you
>> are doing and why.
>>
>
> Sorry, I will describe it in detail.
>
> Our hardware supports insert a specified vlan header for each function
> when send packets. User can enable it with command "ip link set
> <devname> vf <vfid> vlan <vlan id>". For this vlan header is inserted
> by hardware, not from stack, hardware also needs to strip it from
> received packet before upstreaming to stack. In this case, driver
> needs to tell hardware which vlan to insert or strip.
Don't tell me here, rewrite all of your commit messages for this patch
series so that they explain these k inds of details.
That is what I am asking you to do.
Thank you.
next prev parent reply other threads:[~2019-04-12 4:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 12:25 [PATCH net-next 00/12] code optimizations & bugfixes for HNS3 driver Huazhong Tan
2019-04-11 12:25 ` [PATCH net-next 01/12] net: hns3: fix VLAN initialization to be compatible with port base insert VLAN Huazhong Tan
2019-04-11 18:20 ` David Miller
2019-04-12 2:30 ` tanhuazhong
2019-04-12 4:26 ` David Miller [this message]
2019-04-11 12:25 ` [PATCH net-next 02/12] net: hns3: fix VLAN offload handle for VLAN inserted by port Huazhong Tan
2019-04-11 12:25 ` [PATCH net-next 03/12] net: hns3: fix set port based VLAN for PF Huazhong Tan
2019-04-11 12:25 ` [PATCH net-next 04/12] net: hns3: fix set port based VLAN issue for VF Huazhong Tan
2019-04-11 12:25 ` [PATCH net-next 05/12] net: hns3: minor refactor for hns3_rx_checksum Huazhong Tan
2019-04-11 12:25 ` [PATCH net-next 06/12] net: hns3: add hns3_gro_complete for HW GRO process Huazhong Tan
2019-04-11 12:25 ` [PATCH net-next 07/12] net: hns3: always assume no drop TC for performance reason Huazhong Tan
2019-04-11 12:25 ` [PATCH net-next 08/12] net: hns3: divide shared buffer between TC Huazhong Tan
2019-04-11 12:25 ` [PATCH net-next 09/12] net: hns3: set dividual reset level for all RAS and MSI-X errors Huazhong Tan
2019-04-11 12:25 ` [PATCH net-next 10/12] net: hns3: do not initialize MDIO bus when PHY is inexistent Huazhong Tan
2019-04-11 12:25 ` [PATCH net-next 11/12] net: hns3: free the pending skb when clean RX ring Huazhong Tan
2019-04-11 12:25 ` [PATCH net-next 12/12] net: hns3: code optimization for command queue' spin lock Huazhong Tan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190411.212641.809336343201829564.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.com \
--cc=shenjian15@huawei.com \
--cc=tanhuazhong@huawei.com \
--cc=yisen.zhuang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).