All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ashwin Sekhar Thalakalath Kottilveetil <asekhar@marvell.com>,
	"Thomas Monjalon" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Sunil Kumar Kori <skori@marvell.com>,
	"Satha Koteswara Rao Kottidi" <skoteshwar@marvell.com>,
	Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
	Kiran Kumar Kokkilagadda <kirankumark@marvell.com>,
	Satheesh Paul <psatheesh@marvell.com>,
	"Anoob Joseph" <anoobj@marvell.com>,
	Akhil Goyal <gakhil@marvell.com>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] [EXT] Re: [PATCH v3] devtools: add acronyms in dictionary for commit checks
Date: Mon, 20 Sep 2021 11:31:56 +0100	[thread overview]
Message-ID: <56f5cde4-4b4d-7787-47f5-266d06cf55f6@intel.com> (raw)
In-Reply-To: <CO1PR18MB454042D5AFE1395ECCE6E3A1BFA09@CO1PR18MB4540.namprd18.prod.outlook.com>

On 9/20/2021 10:19 AM, Ashwin Sekhar Thalakalath Kottilveetil wrote:
>>> Oh yes, I missed it, sorry.
>>>
>>>>> One more question: why is useful to add? Some people forget
>> uppercases?
>>>>
>>>> Upper case is desired but not really mandatory. This was a suggestion
>>>> put forth to me In one of the reviews.
>>>> https://urldefense.proofpoint.com/v2/url?u=https-
>> 3A__patches.dpdk.org
>>>> _project_dpdk_patch_20210830135231.2610152-2D1-2Dasekhar-
>> 40marvell.co
>>>> m_&d=DwIDaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=pYk-QOhvnkU-
>> _75y0NKSn535ZotEGI
>>>> _E69Py3Ppondk&m=tCLT4AyWr6-
>> VYmqkdbD879kj0uDFhCqF6jjOWfe8Dn4&s=EWthslG
>>>> Cy_OWH4bqcOEKKkweFTe4yHZ-2O5yqiKp39w&e=
>>>>
>>>> I can abandon this change if you feel it is not appropriate to put
>>>> many device specific acronyms in the top level word list.
>>>
>>> No strong opinion, but I think the patch is OK.
>>> David, Ferruh, opinions?
>>>
>>
>> Yes this is suggested to be sure acronyms are uppercase in the patch title.
>>
>> But if an issue can be described in generic concepts, I am for using them to
>> instead of using device specific acronyms, to make commit logs less cryptic.
> Agree that certain commit logs could be re-worded and put in more
> generic terms.
> 
>> Like 'NIC' should be used instead of 'NIX'.
> But NIX and NIC are not exactly interchangeable. NIX refers to a co-processor.
> NIX in conjunction with other co-processors (NPA, LMT etc.) delivers the
> functionality of a NIC.
> 

Got it, my bad, I understood they are same. OK to keep it.

>>
>> Similarly we can try to use long version of CQ/SQ/RQ, although we may need
>> to use them because of limited title length time to time.
>>
>> Rest seems device specific abbreviations we may not escape to use them, so
>> they are OK to me.
> 


  reply	other threads:[~2021-09-20 10:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-17 10:03 [dpdk-dev] [PATCH v1] devtools: add acronyms in dictionary for commit checks Ashwin Sekhar T K
2021-09-17 10:06 ` [dpdk-dev] [PATCH v2] " Ashwin Sekhar T K
2021-09-17 10:58 ` [dpdk-dev] [PATCH v3] " Ashwin Sekhar T K
2021-09-17 11:03   ` Jerin Jacob
2021-11-25 11:30     ` Thomas Monjalon
2021-09-17 12:55   ` Thomas Monjalon
2021-09-17 13:54     ` [dpdk-dev] [EXT] " Ashwin Sekhar Thalakalath Kottilveetil
2021-09-17 14:05       ` Thomas Monjalon
2021-09-17 14:53         ` Ashwin Sekhar Thalakalath Kottilveetil
2021-09-17 16:15           ` Thomas Monjalon
2021-09-20  9:05             ` Ferruh Yigit
2021-09-20  9:19               ` Ashwin Sekhar Thalakalath Kottilveetil
2021-09-20 10:31                 ` Ferruh Yigit [this message]
2021-09-20  9:07   ` [dpdk-dev] " Ferruh Yigit
2021-09-20  9:10     ` Jerin Jacob
2021-09-20 10:32       ` Ferruh Yigit
2021-11-03 16:44         ` Ferruh Yigit
2021-09-20  9:21     ` [dpdk-dev] [EXT] " Ashwin Sekhar Thalakalath Kottilveetil

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=56f5cde4-4b4d-7787-47f5-266d06cf55f6@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=anoobj@marvell.com \
    --cc=asekhar@marvell.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=kirankumark@marvell.com \
    --cc=pbhagavatula@marvell.com \
    --cc=psatheesh@marvell.com \
    --cc=skori@marvell.com \
    --cc=skoteshwar@marvell.com \
    --cc=thomas@monjalon.net \
    /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.