From: Jakub Kicinski <kuba@kernel.org>
To: Guo Ren <guoren@kernel.org>
Cc: andriy.shevchenko@linux.intel.com, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, linux@rasmusvillemoes.dk,
yury.norov@gmail.com, caraitto@google.com, willemb@google.com,
jonolson@google.com, amritha.nambiar@intel.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Guo Ren <guoren@linux.alibaba.com>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH] Revert "cpumask: fix checking valid cpu range"
Date: Mon, 17 Oct 2022 12:53:20 -0700 [thread overview]
Message-ID: <20221017125320.18b54147@kernel.org> (raw)
In-Reply-To: <CAJF2gTTz=Whg+heB95doVnQWVvjNC1bCx1bYLMW4CtybABBGNA@mail.gmail.com>
On Mon, 17 Oct 2022 10:56:05 +0800 Guo Ren wrote:
> Ping Jakub Kicinski <kuba@kernel.org>.
>
> You seem to miss this Revert fixup on cpumask_check(n + 1).
>
> Your patch has merged in v6.1-rc1, but that is not enough.
> https://lore.kernel.org/netdev/166582921612.1299.769135677399153914.git-patchwork-notify@kernel.org/T/#m0111a76380626b2f91e072ecdd5827578d5cbf60
>
> Without the patch, there still is a warning.
Sorry, I don't know what you mean. I was only putting a workaround back
into the core networking code - I'm guessing this patch will silence
the warning that comes from virtio? I haven't looked into that one.
next prev parent reply other threads:[~2022-10-17 19:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-15 13:05 [PATCH] Revert "cpumask: fix checking valid cpu range" guoren
2022-10-15 16:50 ` Guenter Roeck
2022-10-16 2:58 ` Guo Ren
2022-10-16 3:49 ` Guenter Roeck
2022-10-17 2:56 ` Guo Ren
2022-10-17 19:53 ` Jakub Kicinski [this message]
2022-10-18 1:56 ` Guo Ren
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=20221017125320.18b54147@kernel.org \
--to=kuba@kernel.org \
--cc=amritha.nambiar@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=caraitto@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=guoren@kernel.org \
--cc=guoren@linux.alibaba.com \
--cc=jonolson@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=linux@roeck-us.net \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.com \
--cc=yury.norov@gmail.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).