All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hanjun Guo <guohanjun@huawei.com>
To: "lipeng (Y)" <lipeng321@huawei.com>, David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linuxarm@huawei.com>, <salil.mehta@huawei.com>,
	<qumingguang@huawei.com>
Subject: Re: [PATCH V3 net-next 00/17] add some features and fix some bugs for HNS3 driver
Date: Thu, 21 Dec 2017 10:43:07 +0800	[thread overview]
Message-ID: <aa616fc0-0b35-12c4-bb63-d088ef417735@huawei.com> (raw)
In-Reply-To: <5619d233-a0bc-3bd9-daf4-cffb5486b396@huawei.com>

On 2017/12/21 10:27, lipeng (Y) wrote:
> 
> 
> On 2017/12/21 3:28, David Miller wrote:
>> From: Lipeng <lipeng321@huawei.com>
>> Date: Wed, 20 Dec 2017 16:43:02 +0800
>>
>>> This patchset adds some new feature support and fixes some bugs:
>>> [Patch 1/17 - 5/17] add the support to modify/query the tqp number
>>> through ethtool -L/l command, and also fix some related bugs for
>>> change tqp number.
>>> [Patch 6/17 - 9-17] add support vlan tag offload on tx&&rx direction
>>> for pf, and fix some related bugs.
>>> [patch 10/17 - 11/17] fix bugs for auto negotiation.
>>> [patch 12/17] adds support for ethtool command set_pauseparam.
>>> [patch 13/17 - 14/17] add support to update flow control settings after
>>> autoneg.
>>> [patch 15/17 - 17/17] fix some other bugs in net-next.
>> In your From: email field, as well as you and your colleagues signoffs
>> you are not using your full, real, name:
>>
>> ====================
>> From: Lipeng <lipeng321@huawei.com>
> 
> My first name is 'Peng' and Surname is 'Li'.
> But it is usually spelled as 'Lipeng' in one go when referring.
> This is quite usual convention with full names originating from
> China. Surnames comes first, followed by the first name and they
> both are inseparable while they are written as well.
> "Lipeng" is my full real name,  and my sign-off's appear like above.
> 
> 
> The name "lipeng"  is very common in china, many guys in HuaWei have the
> same name "lipeng",
> So my email is lipeng321@huawei.com,  to Distinguish from others.
> 
> other guys who named "lipeng" in huawei ,  their email have an id too,
> such as lipengxxx@huawei.com.
> 
> Wish the explanation is clear.

I think David was expecting two fixes here:

- The first one is that the Author of the patch
  needs to match the first Signed-off-by in
  the patch. In your patches, lots of them show
  that you are the Author but qumingguang is
  in the first Signed-off-by.

- It's better to use first name + last name:
  Peng Li <lipeng321@huawei.com>
  Mingguang Qu <qumingguang@huawei.com>

Thanks
Hanjun

      reply	other threads:[~2017-12-21  2:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-20  8:43 [PATCH V3 net-next 00/17] add some features and fix some bugs for HNS3 driver Lipeng
2017-12-20  8:43 ` [PATCH V3 net-next 01/17] net: hns3: add support to query tqps number Lipeng
2017-12-20  8:43 ` [PATCH V3 net-next 02/17] net: hns3: add support to modify " Lipeng
2017-12-20  8:43 ` [PATCH V3 net-next 03/17] net: hns3: change the returned tqp number by ethtool -x Lipeng
2017-12-20  8:43 ` [PATCH V3 net-next 04/17] net: hns3: Free the ring_data structrue when change tqps Lipeng
2017-12-20  8:43 ` [PATCH V3 net-next 05/17] net: hns3: Get rss_size_max from configuration but not hardcode Lipeng
2017-12-20  8:43 ` [PATCH V3 net-next 06/17] net: hns3: Add a mask initialization for mac_vlan table Lipeng
2017-12-20  8:43 ` [PATCH V3 net-next 07/17] net: hns3: Add vlan offload config command Lipeng
2017-12-20  8:43 ` [PATCH V3 net-next 08/17] net: hns3: Add ethtool related offload command Lipeng
2017-12-20  8:43 ` [PATCH V3 net-next 09/17] net: hns3: Add handling vlan tag offload in bd Lipeng
2017-12-20  8:43 ` [PATCH V3 net-next 10/17] net: hns3: cleanup mac auto-negotiation state query Lipeng
2017-12-20  8:43 ` [PATCH V3 net-next 11/17] net: hns3: fix for getting auto-negotiation state in hclge_get_autoneg Lipeng
2017-12-20  8:43 ` [PATCH V3 net-next 12/17] net: hns3: add support for set_pauseparam Lipeng
2017-12-20  8:43 ` [PATCH V3 net-next 13/17] net: hns3: add support to update flow control settings after autoneg Lipeng
2017-12-20  8:43 ` [PATCH V3 net-next 14/17] net: hns3: add Asym Pause support to phy default features Lipeng
2017-12-20  8:43 ` [PATCH V3 net-next 15/17] net: hns3: add support for querying advertised pause frame by ethtool ethx Lipeng
2017-12-20  8:43 ` [PATCH V3 net-next 16/17] net: hns3: Increase the default depth of bucket for TM shaper Lipeng
2017-12-20  8:43 ` [PATCH V3 net-next 17/17] net: hns3: change TM sched mode to TC-based mode when SRIOV enabled Lipeng
2017-12-20 19:28 ` [PATCH V3 net-next 00/17] add some features and fix some bugs for HNS3 driver David Miller
2017-12-21  1:30   ` lipeng (Y)
2017-12-21  4:04     ` David Miller
2017-12-21  6:57       ` lipeng (Y)
2017-12-21 15:08         ` David Miller
2017-12-21  2:27   ` lipeng (Y)
2017-12-21  2:43     ` Hanjun Guo [this message]

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=aa616fc0-0b35-12c4-bb63-d088ef417735@huawei.com \
    --to=guohanjun@huawei.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=lipeng321@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=qumingguang@huawei.com \
    --cc=salil.mehta@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.