From: Jakub Kicinski <kuba@kernel.org>
To: Joachim Foerster <joachim.foerster@missinglinkelectronics.com>
Cc: "David S . Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Tariq Toukan <tariqt@nvidia.com>,
Gal Pressman <gal@nvidia.com>
Subject: Re: [PATCH] net: Fix special case of empty range in find_next_netdev_feature()
Date: Mon, 26 Jun 2023 14:17:39 -0700 [thread overview]
Message-ID: <20230626141739.54d78c7e@kernel.org> (raw)
In-Reply-To: <20230623142616.144923-1-joachim.foerster@missinglinkelectronics.com>
On Fri, 23 Jun 2023 16:26:16 +0200 Joachim Foerster wrote:
> Fixes: 85db6352fc8a ("net: Fix features skip in for_each_netdev_feature()")
> Cc: stable@vger.kernel.org
Nothing passes @feature with bit 0 set upstream, tho, right?
Fix looks fine, but it doesn't need the fixes tag and CC stable,
since its theoretical/forward looking.
Please repost explaining how we can hit this problem upstream
or with the Fixes/CC stable replaced by a sentence stating that
the problem can't currently be triggered.
--
pw-bot: cr
next prev parent reply other threads:[~2023-06-26 21:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 14:26 [PATCH] net: Fix special case of empty range in find_next_netdev_feature() Joachim Foerster
2023-06-26 21:17 ` Jakub Kicinski [this message]
2023-07-05 13:40 ` Joachim Förster
2023-07-05 16:25 ` Jakub Kicinski
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=20230626141739.54d78c7e@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=gal@nvidia.com \
--cc=joachim.foerster@missinglinkelectronics.com \
--cc=netdev@vger.kernel.org \
--cc=tariqt@nvidia.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 NNTP newsgroup(s).