DPDK patches and discussions
 help / color / mirror / Atom feed
From: Arnon Warshavsky <arnon@qwilt.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>,
	dpdk stable <stable@dpdk.org>,
	 Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [dpdk-dev] [PATCH 1/2] devtools: fix filename in forbidden token check
Date: Mon, 6 Jul 2020 12:50:54 +0300	[thread overview]
Message-ID: <CAKy9EB3pSbSOLxOot29FfOkXrkSZvJz8AQqNTNypsUyts4tdsA@mail.gmail.com> (raw)
In-Reply-To: <20200706080022.3887-1-david.marchand@redhat.com>

On Mon, Jul 6, 2020 at 11:00 AM David Marchand <david.marchand@redhat.com>
wrote:

> Fix displayed filename by adjusting the extraction from the patch.
>
> Before:
> Warning in /lib/librte_eal/linux/eal.c:
>
> After:
> Warning in lib/librte_eal/linux/eal.c:
>
> Fixes: 7413e7f2aeb3 ("devtools: alert on new calls to exit from libs")
> Cc: stable@dpdk.org
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
>  devtools/check-forbidden-tokens.awk | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/devtools/check-forbidden-tokens.awk
> b/devtools/check-forbidden-tokens.awk
> index 8c89de3d4e..f86cbe8dc1 100755
> --- a/devtools/check-forbidden-tokens.awk
> +++ b/devtools/check-forbidden-tokens.awk
> @@ -62,7 +62,7 @@ BEGIN {
>  }
>  END {
>         if (count > 0) {
> -               print "Warning in " substr(last_file,6) ":"
> +               print "Warning in " substr(last_file,7) ":"
>                 print MESSAGE
>                 exit RET_ON_FAIL
>         }
> --
> 2.23.0
>
>
Acked-By: Arnon Warshavsky <arnon@qwilt.com>

      parent reply	other threads:[~2020-07-06  9:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-06  8:00 David Marchand
2020-07-06  8:00 ` [dpdk-dev] [PATCH 2/2] devtools: fix forbidden token David Marchand
2020-07-06  8:56   ` Thomas Monjalon
2020-07-06  9:50 ` Arnon Warshavsky [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=CAKy9EB3pSbSOLxOot29FfOkXrkSZvJz8AQqNTNypsUyts4tdsA@mail.gmail.com \
    --to=arnon@qwilt.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.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).