All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Guo Zhengkui <guozhengkui@vivo.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	shuah@kernel.org, netdev@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	zhengkui_guo@outlook.com
Subject: Re: [PATCH linux-next v3] selftests: net: change fprintf format specifiers
Date: Tue, 22 Mar 2022 00:00:10 +0000	[thread overview]
Message-ID: <164790721070.15202.9703241191384577497.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220319073730.5235-1-guozhengkui@vivo.com>

Hello:

This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Sat, 19 Mar 2022 15:37:30 +0800 you wrote:
> `cur64`, `start64` and `ts_delta` are int64_t. Change format
> specifiers in fprintf from `"%lu"` to `"%" PRId64` to adapt
> to 32-bit and 64-bit systems.
> 
> Signed-off-by: Guo Zhengkui <guozhengkui@vivo.com>
> ---
>  tools/testing/selftests/net/txtimestamp.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)

Here is the summary with links:
  - [linux-next,v3] selftests: net: change fprintf format specifiers
    https://git.kernel.org/netdev/net-next/c/94f19e1ec38f

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2022-03-22  0:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16 11:50 [PATCH] selftests: net: fix warning when compiling selftest/net Guo Zhengkui
2022-03-17  3:22 ` Jakub Kicinski
2022-03-17  6:51   ` Guo Zhengkui
2022-03-18  7:50     ` [PATCH linux-next v2] selftests: net: change fprintf format specifiers Guo Zhengkui
2022-03-18 16:33       ` Jakub Kicinski
2022-03-19  7:09         ` Guo Zhengkui
2022-03-19  7:37         ` [PATCH linux-next v3] " Guo Zhengkui
2022-03-22  0:00           ` patchwork-bot+netdevbpf [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=164790721070.15202.9703241191384577497.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=guozhengkui@vivo.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.org \
    --cc=zhengkui_guo@outlook.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 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.