[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <PH0PR21MB3025FABCB31D555476332158D7959@PH0PR21MB3025.namprd21.prod.outlook.com>
Date: Mon, 25 Jul 2022 21:12:39 +0000
From: "Michael Kelley (LINUX)" <mikelley@...rosoft.com>
To: Randy Dunlap <rdunlap@...radead.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Samuel Holland <samuel@...lland.org>
CC: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Tianyu Lan <Tianyu.Lan@...rosoft.com>,
Joerg Roedel <jroedel@...e.de>, Will Deacon <will@...nel.org>,
"iommu@...ts.linux.dev" <iommu@...ts.linux.dev>,
"linux-hyperv@...r.kernel.org" <linux-hyperv@...r.kernel.org>
Subject: RE: linux-next: Tree for Jul 25 (drivers/iommu/hyperv-iommu.c)
From: Randy Dunlap <rdunlap@...radead.org> Sent: Monday, July 25, 2022 1:33 PM
>
> On 7/25/22 04:18, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20220722:
> >
>
> on x86_64:
> when CONFIG_SMP is not set:
>
> ../drivers/iommu/hyperv-iommu.c: In function ‘hyperv_irq_remapping_alloc’:
> ../drivers/iommu/hyperv-iommu.c:94:43: error: ‘struct irq_common_data’ has no
> member named ‘affinity’
> 94 | cpumask_copy(desc->irq_common_data.affinity, &ioapic_max_cpumask);
>
I'll provide a fix. Looks like this is a side-effect of commit aa0813581b8d from
Samuel Holland.
Michael
Powered by blists - more mailing lists