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, jeroendb@google.com, pkaligineedi@google.com,
shailend@google.com, nathan@kernel.org, ndesaulniers@google.com,
morbo@google.com, justinstitt@google.com,
larysa.zaremba@intel.com, dan.carpenter@linaro.org,
keescook@chromium.org, netdev@vger.kernel.org,
llvm@lists.linux.dev, linux-hardening@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] gve: Minor cleanups
Date: Sat, 11 May 2024 02:00:30 +0000 [thread overview]
Message-ID: <171539283011.14416.2158436781698025205.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240508-gve-comma-v2-0-1ac919225f13@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 08 May 2024 09:32:18 +0100 you wrote:
> Hi,
>
> This short patchset provides two minor cleanups for the gve driver.
>
> These were found by tooling as mentioned in each patch,
> and otherwise by inspection.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] gve: Avoid unnecessary use of comma operator
https://git.kernel.org/netdev/net-next/c/ebb8308eac84
- [net-next,v2,2/2] gve: Use ethtool_sprintf/puts() to fill stats strings
https://git.kernel.org/netdev/net-next/c/ba8bcb012b7d
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-05-11 2:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 8:32 [PATCH net-next v2 0/2] gve: Minor cleanups Simon Horman
2024-05-08 8:32 ` [PATCH net-next v2 1/2] gve: Avoid unnecessary use of comma operator Simon Horman
2024-05-08 8:32 ` [PATCH net-next v2 2/2] gve: Use ethtool_sprintf/puts() to fill stats strings Simon Horman
2024-05-08 17:30 ` Justin Stitt
2024-05-11 2: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=171539283011.14416.2158436781698025205.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jeroendb@google.com \
--cc=justinstitt@google.com \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=larysa.zaremba@intel.com \
--cc=linux-hardening@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=shailend@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 read-only IMAP folder(s) and NNTP newsgroup(s).