From: "Gaëtan Rivet" <grive@u256.net>
To: 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: Fri, 14 Aug 2020 22:28:16 +0200 [thread overview]
Message-ID: <20200814202816.tzmkk6mwumu753cy@u256.net> (raw)
In-Reply-To: <20200814173933.23981-1-stephen@networkplumber.org>
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>
>
> ---
> drivers/net/failsafe/failsafe_ether.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/failsafe/failsafe_ether.c b/drivers/net/failsafe/failsafe_ether.c
> index 2b748bd8b426..70972d67174f 100644
> --- a/drivers/net/failsafe/failsafe_ether.c
> +++ b/drivers/net/failsafe/failsafe_ether.c
> @@ -322,10 +322,10 @@ fs_dev_stats_save(struct sub_device *sdev)
> if (err) {
> uint64_t timestamp = sdev->stats_snapshot.timestamp;
>
> - WARN("Could not access latest statistics from sub-device %d.\n",
> + WARN("Could not access latest statistics from sub-device %d.",
> SUB_ID(sdev));
> if (timestamp != 0)
> - WARN("Using latest snapshot taken before %"PRIu64" seconds.\n",
> + WARN("Using latest snapshot taken before %"PRIu64" seconds.",
> (rte_rdtsc() - timestamp) / rte_get_tsc_hz());
> }
> failsafe_stats_increment
> --
> 2.27.0
>
--
Gaëtan
next prev parent reply other threads:[~2020-08-14 20:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 17:39 [dpdk-dev] [PATCH] net/failsafe: don't double space warning Stephen Hemminger
2020-08-14 20:28 ` Gaëtan Rivet [this message]
2020-08-14 20:30 ` Gaëtan Rivet
2020-08-18 18:32 ` Ferruh Yigit
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=20200814202816.tzmkk6mwumu753cy@u256.net \
--to=grive@u256.net \
--cc=dev@dpdk.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.