From: John Garry <john.g.garry@oracle.com>
To: Jakub Kicinski <kuba@kernel.org>, Jann Horn <jannh@google.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: ethtool: avoid rebuilds on UTS_RELEASE change
Date: Thu, 22 Feb 2024 08:08:34 +0000 [thread overview]
Message-ID: <9e6e933d-be9b-406b-85f4-7b8e3c2f8267@oracle.com> (raw)
In-Reply-To: <20240221113541.76161ac3@kernel.org>
On 21/02/2024 19:35, Jakub Kicinski wrote:
Thanks for including me
> On Wed, 21 Feb 2024 20:25:00 +0100 Jann Horn wrote:
>>> Is this related to John's work from:
>>> https://urldefense.com/v3/__https://lore.kernel.org/all/20240131104851.2311358-1-john.g.garry@oracle.com/__;!!ACWV5N9M2RV99hQ!IghWg9_5HEQ-ng1XiYH9hes6vmgylmcQF5l2RITIrCSB20BzKzOhWWKHrgQZw_DkgKlZRNllglTanuY$
>>> ?
>>
>> Ah, I didn't see his patch, but that seems like he had the same idea
>> (but implemented it less sloppily). You can drop this one then...
>
> No preference on my side, just wanted to make sure we don't have
> to decide within netdev which approach is better, not really our
> wheelhouse :)
I was not going to pursue the change to introduce uts_release, as we can
instead use init_uts_ns.name.release or init_utsname()->release instead.
I think that init_utsname()->release is a bit neater to use, as it
slightly hides the init_uts_ns structure.
@Jann, please feel free to pursue upstreaming the change in this patch with:
Reviewed-by: John Garry <john.g.garry@oracle.com>
However, note that I do have many other changes pending on this subject,
see:
https://github.com/johnpgarry/linux/commits/uts-version-string/
I just need to find a bit of time to update and post them. We also need
to be wary of CONFIG_MODVERSIONS, as discussed in that thread.
Thanks,
John
next prev parent reply other threads:[~2024-02-22 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 19:42 Jann Horn
2024-02-21 19:23 ` Jakub Kicinski
2024-02-21 19:25 ` Jann Horn
2024-02-21 19:35 ` Jakub Kicinski
2024-02-22 8:08 ` John Garry [this message]
2024-02-24 2:10 ` 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=9e6e933d-be9b-406b-85f4-7b8e3c2f8267@oracle.com \
--to=john.g.garry@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jannh@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®