netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: netdev@vger.kernel.org, kernel@pengutronix.de,
	Jakub Kicinski <kuba@kernel.org>,
	Carlos Llamas <cmllamas@google.com>
Subject: Re: [PATCH net 1/2] selftests/net: so_txtime: fix parsing of start time stamp on 32 bit systems
Date: Mon, 2 May 2022 09:50:09 -0400	[thread overview]
Message-ID: <CA+FuTSesQwCwko9xuNyOz7XU1erpFhHtXDttV88TAGjVr4e1tQ@mail.gmail.com> (raw)
In-Reply-To: <20220502094638.1921702-2-mkl@pengutronix.de>

On Mon, May 2, 2022 at 5:46 AM Marc Kleine-Budde <mkl@pengutronix.de> wrote:
>
> This patch fixes the parsing of the cmd line supplied start time on 32
> bit systems. A "long" on 32 bit systems is only 32 bit wide and cannot
> hold a timestamp in nano second resolution.
>
> 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>

Acked-by: Willem de Bruijn <willemb@google.com>

  reply	other threads:[~2022-05-02 13:50 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 [this message]
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

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=CA+FuTSesQwCwko9xuNyOz7XU1erpFhHtXDttV88TAGjVr4e1tQ@mail.gmail.com \
    --to=willemdebruijn.kernel@gmail.com \
    --cc=cmllamas@google.com \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.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).