DPDK patches and discussions
 help / color / mirror / Atom feed
From: "WanRenyong" <wanry@yunsilicon.com>
To: "Thomas Monjalon" <thomas@monjalon.net>
Cc: <dev@dpdk.org>, <ferruh.yigit@amd.com>,
	<stephen@networkplumber.org>,  <qianr@yunsilicon.com>,
	<nana@yunsilicon.com>, <zhangxx@yunsilicon.com>,
	 <xudw@yunsilicon.com>, <jacky@yunsilicon.com>,
	<weihg@yunsilicon.com>
Subject: Re: [PATCH v6 01/15] net/xsc: add xsc PMD framework
Date: Thu, 23 Jan 2025 17:19:24 +0800	[thread overview]
Message-ID: <38e5d6c3-674a-43ca-9cc1-bbd0b1b5a93e@yunsilicon.com> (raw)
In-Reply-To: <2290947.Dhsi8hcfAM@thomas>

On 2025/1/23 15:59, Thomas Monjalon wrote:
> 23/01/2025 06:48, WanRenyong:
>> On 2025/1/22 21:39, Thomas Monjalon wrote:
>>>> +Yunsilicon xsc
>>>> +M: WanRenyong <wanry@yunsilicon.com>
>>>> +M: Na Na <nana@yunsilicon.com>
>>>> +M: Rong Qian <qianr@yunsilicon.com>
>>>> +M: Xiaoxiong Zhang <zhangxx@yunsilicon.com>
>>>> +M: Dongwei Xu <xudw@yunsilicon.com>
>>> Looking at how the names are codified in email addresses,
>>> I feel "Renyong Wan" is the right form for your name in English format.
>>>
>>>
>> Hello Tomas Monjalon,
>>
>> Yes, you are right, but if I use "Renyong Wan" as my English name, every
>> patch alway gets a misspelling warning from checkpatch. :(
>> It's really annoying. If it isn't unacceptable to DPDK for  using
>> "WanRenyong" as my name, I don't mind of it too.
> Can't you set "Renyong Wan" in your .gitconfig?
> I think it would solve your issue.
>
>
Hello Tomas Monjalon,

I tried it , there are still a few warnings from checkpatch like below:

WARNING:TYPO_SPELLING: 'Wan' may be misspelled - perhaps 'Want'?
#8:
Renyong Wan (15):
         ^^^

If DPDK accept it , I'll change my name to "Renyong Wan" in the next 
version.

Thank you.

-- 
Best regards,
WanRenyong

  reply	other threads:[~2025-01-23  9:19 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-20 11:15 [PATCH v6 00/15] XSC PMD for Yunsilicon NICs WanRenyong
2025-01-20 11:14 ` [PATCH v6 01/15] net/xsc: add xsc PMD framework WanRenyong
2025-01-22 13:39   ` Thomas Monjalon
2025-01-23  5:48     ` WanRenyong
2025-01-23  7:59       ` Thomas Monjalon
2025-01-23  9:19         ` WanRenyong [this message]
2025-01-23 14:41           ` Thomas Monjalon
2025-01-23 16:09       ` Stephen Hemminger
2025-01-20 11:14 ` [PATCH v6 02/15] net/xsc: add xsc device initialization WanRenyong
2025-01-20 11:14 ` [PATCH v6 03/15] net/xsc: add xsc mailbox WanRenyong
2025-01-20 18:18   ` Stephen Hemminger
2025-01-21  2:39     ` WanRenyong
2025-01-20 18:19   ` Stephen Hemminger
2025-01-21  3:31     ` WanRenyong
2025-01-20 11:14 ` [PATCH v6 04/15] net/xsc: add xsc dev ops to support VFIO driver WanRenyong
2025-01-20 11:14 ` [PATCH v6 05/15] net/xsc: add PCT interfaces WanRenyong
2025-01-20 18:24   ` Stephen Hemminger
2025-01-21  3:44     ` WanRenyong
2025-01-20 11:14 ` [PATCH v6 06/15] net/xsc: initialize xsc representors WanRenyong
2025-01-20 19:06   ` Stephen Hemminger
2025-01-21  5:27     ` WanRenyong
2025-01-20 11:14 ` [PATCH v6 07/15] net/xsc: add ethdev configure and RSS ops WanRenyong
2025-01-20 11:14 ` [PATCH v6 08/15] net/xsc: add Rx and Tx queue setup WanRenyong
2025-01-20 18:16   ` Stephen Hemminger
2025-01-21  3:21     ` WanRenyong
2025-01-20 11:14 ` [PATCH v6 09/15] net/xsc: add ethdev start WanRenyong
2025-01-20 11:14 ` [PATCH v6 10/15] net/xsc: add ethdev stop and close WanRenyong
2025-01-20 11:14 ` [PATCH v6 11/15] net/xsc: add ethdev Rx burst WanRenyong
2025-01-20 11:14 ` [PATCH v6 12/15] net/xsc: add ethdev Tx burst WanRenyong
2025-01-20 11:15 ` [PATCH v6 13/15] net/xsc: add basic stats ops WanRenyong
2025-01-20 11:15 ` [PATCH v6 14/15] net/xsc: add ethdev infos get WanRenyong
2025-01-20 11:15 ` [PATCH v6 15/15] net/xsc: add ethdev link and MTU ops WanRenyong

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=38e5d6c3-674a-43ca-9cc1-bbd0b1b5a93e@yunsilicon.com \
    --to=wanry@yunsilicon.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=jacky@yunsilicon.com \
    --cc=nana@yunsilicon.com \
    --cc=qianr@yunsilicon.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    --cc=weihg@yunsilicon.com \
    --cc=xudw@yunsilicon.com \
    --cc=zhangxx@yunsilicon.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).