[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id:
<172808404024.2772330.2975585273609596688.git-patchwork-notify@kernel.org>
Date: Fri, 04 Oct 2024 23:20:40 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Michael Kelley <mhkelley58@...il.com>
Cc: kys@...rosoft.com, haiyangz@...rosoft.com, wei.liu@...nel.org,
decui@...rosoft.com, tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
dave.hansen@...ux.intel.com, x86@...nel.org, hpa@...or.com, joro@...tes.org,
will@...nel.org, robin.murphy@....com, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
James.Bottomley@...senPartnership.com, martin.petersen@...cle.com,
iommu@...ts.linux.dev, netdev@...r.kernel.org, linux-hyperv@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: [PATCH 0/5] hyper-v: Don't assume cpu_possible_mask is dense
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Wed, 2 Oct 2024 20:53:28 -0700 you wrote:
> From: Michael Kelley <mhklinux@...look.com>
>
> Code specific to Hyper-V guests currently assumes the cpu_possible_mask
> is "dense" -- i.e., all bit positions 0 thru (nr_cpu_ids - 1) are set,
> with no "holes". Therefore, num_possible_cpus() is assumed to be equal
> to nr_cpu_ids.
>
> [...]
Here is the summary with links:
- [1/5] x86/hyperv: Don't assume cpu_possible_mask is dense
(no matching commit)
- [2/5] Drivers: hv: Don't assume cpu_possible_mask is dense
(no matching commit)
- [3/5] iommu/hyper-v: Don't assume cpu_possible_mask is dense
(no matching commit)
- [4/5] scsi: storvsc: Don't assume cpu_possible_mask is dense
(no matching commit)
- [net-next,5/5] hv_netvsc: Don't assume cpu_possible_mask is dense
https://git.kernel.org/netdev/net-next/c/c86ab60b92d1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists