From: "Gavin Hu (Arm Technology China)" <Gavin.Hu@arm.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
nd <nd@arm.com>, "stable@dpdk.org" <stable@dpdk.org>,
nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH v1] devtools: fix wrong headline lowercase for arm
Date: Thu, 20 Dec 2018 16:01:55 +0000 [thread overview]
Message-ID: <AM6PR08MB31603557B3B74FE8961593FB8FBF0@AM6PR08MB3160.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <3220337.l9tPYBC6Td@xps>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Thursday, December 20, 2018 11:57 PM
> To: Gavin Hu (Arm Technology China) <Gavin.Hu@arm.com>
> Cc: dev@dpdk.org; bruce.richardson@intel.com; ferruh.yigit@intel.com;
> Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>; nd
> <nd@arm.com>; stable@dpdk.org
> Subject: Re: [PATCH v1] devtools: fix wrong headline lowercase for arm
>
> 20/12/2018 16:52, Gavin Hu:
> > Change to the new wording according to Arm corp:
> > https://mails.dpdk.org/archives/dev/2018-October/115174.html
> > otherwise, "Wrong headline lowercase" may be falsely reported.
> >
> > Fixes: f146ada21d1e ("scripts: add more git log checks")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Gavin Hu <gavin.hu@arm.com>
> > ---
> > --- a/devtools/check-git-log.sh
> > +++ b/devtools/check-git-log.sh
> > - -e ':.*\<arm\>' \
> > - -e ':.*\<armv7\>' \
> > - -e ':.*\<armv8\>' \
> > + -e ':.*\<(Arm|ARM)\>' \
>
> Are you saying that we should not write "Arm"?
> I thought it was the right spelling when talking about the company.
Not sure if Arm, as a company name will appear on the patch headline.
Anyway I will remove Arm here in V2.
>
> > + -e ':.*\<(Armv7|ARMv7|ArmV7|armV7|ARMV7)\>' \
> > + -e ':.*\<(Armv8|ARMv8|ArmV8|armV8|ARMV8)\>' \
>
>
>
prev parent reply other threads:[~2018-12-20 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 15:52 Gavin Hu
2018-12-20 15:57 ` Thomas Monjalon
2018-12-20 16:01 ` Gavin Hu (Arm Technology China) [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=AM6PR08MB31603557B3B74FE8961593FB8FBF0@AM6PR08MB3160.eurprd08.prod.outlook.com \
--to=gavin.hu@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=nd@arm.com \
--cc=stable@dpdk.org \
--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 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).