From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Gaëtan Rivet" <grive@u256.net>,
"Stephen Hemminger" <stephen@networkplumber.org>
Cc: dev@dpdk.org, matan@mellanox.com
Subject: Re: [dpdk-dev] [PATCH] net/failsafe: don't double space warning
Date: Tue, 18 Aug 2020 19:32:45 +0100 [thread overview]
Message-ID: <06b3b6f4-4ecb-ba2e-5d40-a7552212821c@intel.com> (raw)
In-Reply-To: <20200814203013.udvl3mjtih7rihdh@u256.net>
On 8/14/2020 9:30 PM, Gaëtan Rivet wrote:
> On 14/08/20 22:28 +0200, Gaëtan Rivet wrote:
>> On 14/08/20 10:39 -0700, Stephen Hemminger wrote:
>>> Already get a newline from WARN() macro call.
>>>
>>> Fixes: 9dda3e3393c2 ("net/failsafe: add timestamp to stats snapshot")
>>> Cc: matan@mellanox.com
>>> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>>
>> Acked-by: Gaetan Rivet <grive@u256.net>
>>
>
> Ah, I forgot: the patch itself is fine, but it should be backported
> probably. Missing Cc: stable, Fixes, and the title should be reworded "fix
> double space warning" I think.
>
Applied to dpdk-next-net/main, thanks.
(stable tag added, title updated as suggested)
prev parent reply other threads:[~2020-08-18 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 17:39 Stephen Hemminger
2020-08-14 20:28 ` Gaëtan Rivet
2020-08-14 20:30 ` Gaëtan Rivet
2020-08-18 18:32 ` Ferruh Yigit [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=06b3b6f4-4ecb-ba2e-5d40-a7552212821c@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=grive@u256.net \
--cc=matan@mellanox.com \
--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).