From: patchwork-bot+netdevbpf@kernel.org
To: Simon Horman <horms@kernel.org>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, pantelis.antoniou@gmail.com,
geert@linux-m68k.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 0/2] net: ethernet: freescale: Use %pa to format resource_size_t
Date: Tue, 15 Oct 2024 18:00:42 +0000 [thread overview]
Message-ID: <172901524224.1243233.8750809850342370605.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241014-net-pa-fmt-v1-0-dcc9afb8858b@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 14 Oct 2024 11:48:06 +0100 you wrote:
> Hi,
>
> This short series addersses the formatting of variables of
> type resource_size_t in freescale drivers.
>
> The correct format string for resource_size_t is %pa which
> acts on the address of the variable to be formatted [1].
>
> [...]
Here is the summary with links:
- [1/2] net: fec_mpc52xx_phy: Use %pa to format resource_size_t
https://git.kernel.org/netdev/net-next/c/020bfdc4ed94
- [2/2] net: ethernet: fs_enet: Use %pa to format resource_size_t
https://git.kernel.org/netdev/net-next/c/45fe45fada26
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-10-15 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 10:48 [PATCH 0/2] net: ethernet: freescale: Use %pa to format resource_size_t Simon Horman
2024-10-14 10:48 ` [PATCH 1/2] net: fec_mpc52xx_phy: " Simon Horman
2024-10-14 10:48 ` [PATCH 2/2] net: ethernet: fs_enet: " Simon Horman
2024-10-15 7:24 ` [PATCH 0/2] net: ethernet: freescale: " Daniel Machon
2024-10-15 12:10 ` Simon Horman
2024-10-15 18: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=172901524224.1243233.8750809850342370605.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geert@linux-m68k.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pantelis.antoniou@gmail.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).