From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Yury Norov <yury.norov@gmail.com>, David Miller <davem@davemloft.net>
Cc: Jakub Kicinski <kuba@kernel.org>,
Networking <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: duplicate patches in the bitmap tree
Date: Thu, 9 Feb 2023 13:02:24 +1100 [thread overview]
Message-ID: <20230209130224.76c7f357@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1490 bytes --]
Hi all,
The following commits are also in the net-next tree as different commits
(but the same patches):
2386459394d2 ("lib/cpumask: update comment for cpumask_local_spread()")
a99b18849bc8 ("net/mlx5e: Improve remote NUMA preferences used for the IRQ affinity hints")
af547a927f9f ("sched/topology: Introduce for_each_numa_hop_mask()")
439829e1bfba ("sched/topology: Introduce sched_numa_hop_mask()")
c0d13fba970d ("lib/cpumask: reorganize cpumask_local_spread() logic")
8ec0ffa233ab ("cpumask: improve on cpumask_local_spread() locality")
6139966175ca ("sched: add sched_numa_find_nth_cpu()")
ded3cee7db80 ("cpumask: introduce cpumask_nth_and_andnot")
These are commits
2ac4980c57f5 ("lib/cpumask: update comment for cpumask_local_spread()")
2acda57736de ("net/mlx5e: Improve remote NUMA preferences used for the IRQ affinity hints")
06ac01721f7d ("sched/topology: Introduce for_each_numa_hop_mask()")
9feae65845f7 ("sched/topology: Introduce sched_numa_hop_mask()")
b1beed72b8b7 ("lib/cpumask: reorganize cpumask_local_spread() logic")
406d394abfcd ("cpumask: improve on cpumask_local_spread() locality")
cd7f55359c90 ("sched: add sched_numa_find_nth_cpu()")
62f4386e564d ("cpumask: introduce cpumask_nth_and_andnot")
in the net-next tree.
There are some slight differences (I got a conflict merging the bitmap
tree today), but the net-next series is newer than the bitmap tree one ...
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-02-09 2:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 2:02 Stephen Rothwell [this message]
2023-02-09 2:22 ` linux-next: duplicate patches in the bitmap tree Yury Norov
-- strict thread matches above, loose matches on Subject: below --
2025-07-08 23:08 Stephen Rothwell
2025-07-08 23:13 ` Yury Norov
2025-08-01 1:27 Stephen Rothwell
2025-08-01 12:30 ` Yury Norov
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=20230209130224.76c7f357@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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