From: Carlos Llamas <cmllamas@google.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: netdev@vger.kernel.org, kernel@pengutronix.de,
Jakub Kicinski <kuba@kernel.org>,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH net 2/2] selftests/net: so_txtime: usage(): fix documentation of default clock
Date: Mon, 2 May 2022 13:59:48 +0000 [thread overview]
Message-ID: <Ym/j1PGE2NWJ4OQz@google.com> (raw)
In-Reply-To: <20220502094638.1921702-3-mkl@pengutronix.de>
On Mon, May 02, 2022 at 11:46:38AM +0200, Marc Kleine-Budde wrote:
> The program uses CLOCK_TAI as default clock since it was added to the
> Linux repo. In commit:
> | 040806343bb4 ("selftests/net: so_txtime multi-host support")
> a help text stating the wrong default clock was added.
>
> This patch fixes the help text.
>
> Fixes: 040806343bb4 ("selftests/net: so_txtime multi-host support")
> Cc: Carlos Llamas <cmllamas@google.com>
> Cc: Willem de Bruijn <willemb@google.com>
> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
> ---
LGTM, thanks.
Reviewed-by: Carlos Llamas <cmllamas@google.com>
--
Carlos Llamas
prev parent reply other threads:[~2022-05-02 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 9:46 [PATCH net 1/2] selftests/net: so_txtime: fix parsing on 32 bit systems and help text Marc Kleine-Budde
2022-05-02 9:46 ` [PATCH net 1/2] selftests/net: so_txtime: fix parsing of start time stamp on 32 bit systems Marc Kleine-Budde
2022-05-02 13:50 ` Willem de Bruijn
2022-05-02 13:58 ` Carlos Llamas
2022-05-03 11:30 ` patchwork-bot+netdevbpf
2022-05-02 9:46 ` [PATCH net 2/2] selftests/net: so_txtime: usage(): fix documentation of default clock Marc Kleine-Budde
2022-05-02 13:50 ` Willem de Bruijn
2022-05-02 13:59 ` Carlos Llamas [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=Ym/j1PGE2NWJ4OQz@google.com \
--to=cmllamas@google.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.com \
/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).