From: patchwork-bot+netdevbpf@kernel.org
To: John Garry <john.g.garry@oracle.com>
Cc: jiri@resnulli.us, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, gregkh@linuxfoundation.org,
netdev@vger.kernel.org, linux-staging@lists.linux.dev,
masahiroy@kernel.org
Subject: Re: [PATCH net-next 0/3] net/staging: Don't bother filling in ethtool driver version
Date: Sat, 24 Feb 2024 03:10:32 +0000 [thread overview]
Message-ID: <170874423274.898.17692880234682888016.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240222090042.12609-1-john.g.garry@oracle.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 22 Feb 2024 09:00:39 +0000 you wrote:
> The drivers included in this series set the ethtool driver version to the
> same as the default, UTS_RELEASE, so don't both doing this.
>
> As noted by Masahiro in [0], with CONFIG_MODVERSIONS=y, some drivers could
> be built as modules against a different kernel tree with differing
> UTS_RELEASE. As such, these changes could lead to a change in behaviour.
> However, defaulting to the core kernel UTS_RELEASE would be expected
> behaviour.
>
> [...]
Here is the summary with links:
- [net-next,1/3] rocker: Don't bother filling in ethtool driver version
https://git.kernel.org/netdev/net-next/c/23fe265fbfbc
- [net-next,2/3] net: team: Don't bother filling in ethtool driver version
https://git.kernel.org/netdev/net-next/c/0a4e1b453a8a
- [3/3] staging: octeon: Don't bother filling in ethtool driver version
(no matching commit)
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-02-24 3:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 9:00 [PATCH net-next 0/3] net/staging: Don't bother filling in ethtool driver version John Garry
2024-02-22 9:00 ` [PATCH net-next 1/3] rocker: " John Garry
2024-02-22 9:00 ` [PATCH net-next 2/3] net: team: " John Garry
2024-02-22 9:00 ` [PATCH 3/3] staging: octeon: " John Garry
2024-02-22 13:24 ` [PATCH net-next 0/3] net/staging: " Jiri Pirko
2024-02-24 3:10 ` 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=170874423274.898.17692880234682888016.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jiri@resnulli.us \
--cc=john.g.garry@oracle.com \
--cc=kuba@kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.