lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAK8P3a2YiGm=2TSKGotXRR3vJjfv+xhyZuD-Law57UDiagHZxg@mail.gmail.com> Date: Sat, 25 Sep 2021 19:38:23 +0200 From: Arnd Bergmann <arnd@...db.de> To: Sergio Paracuellos <sergio.paracuellos@...il.com> Cc: Thomas Bogendoerfer <tsbogend@...ha.franken.de>, Rob Herring <robh@...nel.org>, Arnd Bergmann <arnd@...db.de>, Catalin Marinas <catalin.marinas@....com>, Liviu Dudau <Liviu.Dudau@....com>, Bjorn Helgaas <bhelgaas@...gle.com>, Matthias Brugger <matthias.bgg@...il.com>, gregkh <gregkh@...uxfoundation.org>, "open list:BROADCOM NVRAM DRIVER" <linux-mips@...r.kernel.org>, linux-pci <linux-pci@...r.kernel.org>, linux-staging@...ts.linux.dev, neil@...wn.name, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 4/6] PCI: allow architecture specific implementation of pci_remap_iospace() On Fri, Sep 24, 2021 at 11:11 PM Sergio Paracuellos <sergio.paracuellos@...il.com> wrote: > > pci_remap_iospace() was originally meant as an architecture specific helper, > but it moved into generic code after all architectures had the same requirements. > MIPS has different requirements so it should not be shared. The way for doing > this will be using a macro 'pci_remap_iospace' defined for those architectures > that need a special treatement. Hence, put core api function inside preprocesor > conditional code for 'pci_remap_iospace' definition. > > Signed-off-by: Sergio Paracuellos <sergio.paracuellos@...il.com> Acked-by: Arnd Bergmann <arnd@...db.de>
Powered by blists - more mailing lists