DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Joseph, Anoob" <Anoob.Joseph@cavium.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "Jacob, Jerin" <Jerin.JacobKollanukkaran@cavium.com>,
	"Athreya, Narayana Prasad" <NarayanaPrasad.Athreya@cavium.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] devtools: add exception for OCTEON TX
Date: Wed, 17 Oct 2018 05:26:16 +0000	[thread overview]
Message-ID: <SN6PR07MB4911DE25914C98C4DE044D57F8FF0@SN6PR07MB4911.namprd07.prod.outlook.com> (raw)
In-Reply-To: <1539176482-31053-1-git-send-email-anoob.joseph@caviumnetworks.com>

Hi Thomas,

Can you review this patch and let me know your comments?

Thanks,
Anoob

> -----Original Message-----
> From: Joseph, Anoob
> Sent: 10 October 2018 18:31
> To: Thomas Monjalon <thomas@monjalon.net>
> Cc: Joseph, Anoob <Anoob.Joseph@cavium.com>; Jacob, Jerin
> <Jerin.JacobKollanukkaran@cavium.com>; Athreya, Narayana Prasad
> <NarayanaPrasad.Athreya@cavium.com>; dev@dpdk.org
> Subject: [PATCH] devtools: add exception for OCTEON TX
> 
> The 'TX' in OCTEON TX would cause a warning. Adding an exception for that.
> 
> OCTEON TX is a registered product under Cavium
> 
> Signed-off-by: Anoob Joseph <anoob.joseph@caviumnetworks.com>
> ---
>  devtools/check-git-log.sh | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/devtools/check-git-log.sh b/devtools/check-git-log.sh index
> 97dae4b..9dce7e0 100755
> --- a/devtools/check-git-log.sh
> +++ b/devtools/check-git-log.sh
> @@ -116,6 +116,8 @@ bad=$(echo "$headlines" | grep -E --color=always \
>  	-e ':.*\<[Vv]lan\>' \
>  	-e ':.*\<vdpa\>' \
>  	-e ':.*\<vsi\>' \
> +	| grep \
> +	-v ':.*\<OCTEON\ TX\>' \
>  	| sed 's,^,\t,')
>  [ -z "$bad" ] || printf "Wrong headline lowercase:\n$bad\n"
> 
> --
> 2.7.4

  reply	other threads:[~2018-10-17  5:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10 13:01 Anoob Joseph
2018-10-17  5:26 ` Joseph, Anoob [this message]
2018-10-25 14:50 ` Thomas Monjalon

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=SN6PR07MB4911DE25914C98C4DE044D57F8FF0@SN6PR07MB4911.namprd07.prod.outlook.com \
    --to=anoob.joseph@cavium.com \
    --cc=Jerin.JacobKollanukkaran@cavium.com \
    --cc=NarayanaPrasad.Athreya@cavium.com \
    --cc=dev@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).