From: Thomas Monjalon <thomas@monjalon.net>
To: Ashwin Sekhar Thalakalath Kottilveetil <asekhar@marvell.com>
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>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.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: Fri, 17 Sep 2021 18:15:39 +0200 [thread overview]
Message-ID: <1890938.tUBTFp5uOv@thomas> (raw)
In-Reply-To: <CO1PR18MB454038559C5DC1359DE66C85BFDD9@CO1PR18MB4540.namprd18.prod.outlook.com>
17/09/2021 16:53, Ashwin Sekhar Thalakalath Kottilveetil:
> From: Thomas Monjalon <thomas@monjalon.net>
> > 17/09/2021 15:54, Ashwin Sekhar Thalakalath Kottilveetil:
> > > From: Thomas Monjalon <thomas@monjalon.net>
> > > > 17/09/2021 12:58, Ashwin Sekhar T K:
> > > > > Update word list with Marvell specific acronyms.
[...]
> > Please add details in the commit log so we understand they are Marvell
> > acronyms.
> Commit log already mentions these are Marvell specific acronyms. I did not
> add explanation for each of them as this would make the message too long.
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://patches.dpdk.org/project/dpdk/patch/20210830135231.2610152-1-asekhar@marvell.com/
>
> 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?
next prev parent reply other threads:[~2021-09-17 16:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 10:03 [dpdk-dev] [PATCH v1] " 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 [this message]
2021-09-20 9:05 ` Ferruh Yigit
2021-09-20 9:19 ` Ashwin Sekhar Thalakalath Kottilveetil
2021-09-20 10:31 ` Ferruh Yigit
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=1890938.tUBTFp5uOv@thomas \
--to=thomas@monjalon.net \
--cc=anoobj@marvell.com \
--cc=asekhar@marvell.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--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 \
/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).