From: Jiri Pirko <jiri@resnulli.us>
To: John Garry <john.g.garry@oracle.com>
Cc: 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: Thu, 22 Feb 2024 14:24:25 +0100 [thread overview]
Message-ID: <ZddLCZ8D-qe2nOP_@nanopsycho> (raw)
In-Reply-To: <20240222090042.12609-1-john.g.garry@oracle.com>
Thu, Feb 22, 2024 at 10:00:39AM CET, john.g.garry@oracle.com 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.
>
>These patches are for netdev and staging trees, and I hope that the
>respective maintainers can pick up the patches separately.
>
>[0] https://lore.kernel.org/all/CAK7LNASfTW+OMk1cJJWb4E6P+=k0FEsm_=6FDfDF_mTrxJCSMQ@mail.gmail.com/
>
>John Garry (3):
> rocker: Don't bother filling in ethtool driver version
> net: team: Don't bother filling in ethtool driver version
> staging: octeon: Don't bother filling in ethtool driver version
>
> drivers/net/ethernet/rocker/rocker_main.c | 2 --
> drivers/net/team/team.c | 2 --
> drivers/staging/octeon/ethernet-mdio.c | 2 --
> 3 files changed, 6 deletions(-)
The set looks fine to me.
Reviewed-by: Jiri Pirko <jiri@nvidia.com>
next prev parent reply other threads:[~2024-02-22 13:24 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 ` Jiri Pirko [this message]
2024-02-24 3:10 ` [PATCH net-next 0/3] net/staging: " patchwork-bot+netdevbpf
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=ZddLCZ8D-qe2nOP_@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--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.