[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <00c5a9e2-1876-e8d1-68f3-2be6d3bd38cb@huawei.com>
Date: Thu, 6 Jan 2022 17:45:24 +0000
From: John Garry <john.garry@...wei.com>
To: Niklas Schnelle <schnelle@...ux.ibm.com>,
Arnd Bergmann <arnd@...nel.org>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Nick Hu <nickhu@...estech.com>,
Greentime Hu <green.hu@...il.com>,
Vincent Chen <deanbo422@...il.com>,
"Paul Walmsley" <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>, Guo Ren <guoren@...nel.org>
CC: <linux-kernel@...r.kernel.org>, <linux-arch@...r.kernel.org>,
<linux-pci@...r.kernel.org>, <linux-riscv@...ts.infradead.org>,
<linux-csky@...r.kernel.org>
Subject: Re: [RFC 00/32] Kconfig: Introduce HAS_IOPORT and LEGACY_PCI options
Hi Niklas,
On 27/12/2021 16:42, Niklas Schnelle wrote:
> I performed the following testing:
>
> - On s390 this series on top of v5.16-rc7 builds with allyesconfig i.e. the
> HAS_IOPORT=n case.
Are you sure that allyesconfig gives HAS_IOPORT=n? Indeed I see no
mechanism is always disallow HAS_IOPORT for s390 (which I think we would
want).
> It also builds with defconfig and the resulting kernel
> appears fully functional including tests with PCI devices.
Thanks,
Johnw
Powered by blists - more mailing lists