Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Edward Cree <ecree.xilinx@gmail.com>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
	Heiner Kallweit <hkallweit1@gmail.com>,
	nic_swsd@realtek.com, "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Jiawen Wu <jiawenwu@trustnetic.com>,
	Mengyuan Lou <mengyuanlou@net-swift.com>,
	Andrew Lunn <andrew@lunn.ch>,
	Russell King <linux@armlinux.org.uk>
Subject: Re: Patch "net: move ethtool-related netdev state into its own struct" has been added to the 6.10-stable tree
Date: Mon, 5 Aug 2024 21:27:08 -0400	[thread overview]
Message-ID: <ZrF77NoLb0TqRnkq@sashalap> (raw)
In-Reply-To: <65f0f054-2de7-572e-d6aa-926a0f3598f4@gmail.com>

On Mon, Aug 05, 2024 at 01:45:18PM +0100, Edward Cree wrote:
>On 05/08/2024 13:19, Sasha Levin wrote:
>> This is a note to let you know that I've just added the patch titled
>>
>>     net: move ethtool-related netdev state into its own struct
>>
>> to the 6.10-stable tree which can be found at:
>>     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>>
>> The filename of the patch is:
>>      net-move-ethtool-related-netdev-state-into-its-own-s.patch
>> and it can be found in the queue-6.10 subdirectory.
>>
>> If you, or anyone else, feels it should not be added to the stable tree,
>> please let <stable@vger.kernel.org> know about it.
>
>This, and the series it's from, are absolutely not -stable material.
>The commits do not fix any existing bugs, they are in support of new
> features (netlink dumping of RSS contexts), and are a fairly large
> and complex set of changes, which have not even stabilised yet — we
> have already found issues both within the set and exposed by it in
> other code, which are being fixed for 6.11.
>
>> commit e331e73ff4c5c89a7f51a465ae40a7ad9fcd7a28
>> Author: Edward Cree <ecree.xilinx@gmail.com>
>> Date:   Thu Jun 27 16:33:46 2024 +0100
>>
>>     net: move ethtool-related netdev state into its own struct
>>
>>     [ Upstream commit 3ebbd9f6de7ec6d538639ebb657246f629ace81e ]
>>
>>     net_dev->ethtool is a pointer to new struct ethtool_netdev_state, which
>>      currently contains only the wol_enabled field.
>>
>>     Suggested-by: Jakub Kicinski <kuba@kernel.org>
>>     Signed-off-by: Edward Cree <ecree.xilinx@gmail.com>
>>     Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
>>     Link: https://patch.msgid.link/293a562278371de7534ed1eb17531838ca090633.1719502239.git.ecree.xilinx@gmail.com
>>     Signed-off-by: Jakub Kicinski <kuba@kernel.org>
>>     Stable-dep-of: 7195f0ef7f5b ("ethtool: fix setting key and resetting indir at once")
>>     Signed-off-by: Sasha Levin <sashal@kernel.org>
>
>As far as I can tell, 7195f0ef7f5b should backport fairly cleanly
> to 6.10 with only simple textual fuzz.
>It should not be necessary to backport the "ethtool: track custom
> RSS contexts in the core" series to support this.
>
>The above NAK also applies to the backports of:
>     net-ethtool-attach-an-xarray-of-custom-rss-contexts-.patch
>     net-ethtool-record-custom-rss-contexts-in-the-xarray.patch
>     net-ethtool-add-a-mutex-protecting-rss-contexts.patch
> which were notified at the same time.

Makes sense! I've modified the backport of 7195f0ef7f5b ("ethtool: fix
setting key and resetting indir at once") as proposed.

-- 
Thanks,
Sasha

      reply	other threads:[~2024-08-06  1:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240805121930.2475956-1-sashal@kernel.org>
2024-08-05 12:45 ` Patch "net: move ethtool-related netdev state into its own struct" has been added to the 6.10-stable tree Edward Cree
2024-08-06  1:27   ` Sasha Levin [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=ZrF77NoLb0TqRnkq@sashalap \
    --to=sashal@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=ecree.xilinx@gmail.com \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=jiawenwu@trustnetic.com \
    --cc=kuba@kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mengyuanlou@net-swift.com \
    --cc=nic_swsd@realtek.com \
    --cc=pabeni@redhat.com \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /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