patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, stable@dpdk.org,
	Stephen Hemminger <stephen@networkplumber.org>,
	Arnon Warshavsky <arnon@qwilt.com>
Subject: Re: [PATCH] devtools: fix comment detection in forbidden token check
Date: Thu, 27 Jan 2022 17:20:21 +0100	[thread overview]
Message-ID: <3334932.QJadu78ljV@thomas> (raw)
In-Reply-To: <20220127105511.4397-1-david.marchand@redhat.com>

27/01/2022 11:55, David Marchand:
> After a comment section was detected, passing to a new hunk was not seen
> as ending the section and all subsequent hunks were ignored.
> 
> Fixes: 7413e7f2aeb3 ("devtools: alert on new calls to exit from libs")
> Cc: stable@dpdk.org
> 
> Reported-by: Thomas Monjalon <thomas@monjalon.net>
> Signed-off-by: David Marchand <david.marchand@redhat.com>

Applied, thanks




      reply	other threads:[~2022-01-27 16:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 10:55 David Marchand
2022-01-27 16:20 ` Thomas Monjalon [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=3334932.QJadu78ljV@thomas \
    --to=thomas@monjalon.net \
    --cc=arnon@qwilt.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.org \
    /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).