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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191106182857.GA21062@lst.de>
Date:   Wed, 6 Nov 2019 19:28:57 +0100
From:   Christoph Hellwig <hch@....de>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:     Palmer Dabbelt <palmer@...belt.com>,
        Christoph Hellwig <hch@....de>,
        "linux-ia64@...r.kernel.org" <linux-ia64@...r.kernel.org>,
        Linux-sh list <linux-sh@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Guo Ren <guoren@...nel.org>,
        sparclinux <sparclinux@...r.kernel.org>,
        linux-riscv@...ts.infradead.org,
        Vincent Chen <deanbo422@...il.com>,
        Linux-Arch <linux-arch@...r.kernel.org>,
        linux-s390 <linux-s390@...r.kernel.org>,
        "open list:QUALCOMM HEXAGON..." <linux-hexagon@...r.kernel.org>,
        the arch/x86 maintainers <x86@...nel.org>,
        arcml <linux-snps-arc@...ts.infradead.org>,
        linux-xtensa@...ux-xtensa.org, Arnd Bergmann <arnd@...db.de>,
        linux-m68k <linux-m68k@...ts.linux-m68k.org>,
        Openrisc <openrisc@...ts.librecores.org>,
        Greentime Hu <green.hu@...il.com>,
        MTD Maling List <linux-mtd@...ts.infradead.org>,
        Guan Xuetao <gxt@....edu.cn>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        Michal Simek <monstr@...str.eu>,
        Parisc List <linux-parisc@...r.kernel.org>,
        linux-mips@...r.kernel.org, alpha <linux-alpha@...r.kernel.org>,
        nios2-dev@...ts.rocketboards.org
Subject: Re: [PATCH 11/21] asm-generic: don't provide ioremap for CONFIG_MMU

On Wed, Nov 06, 2019 at 07:16:38PM +0100, Geert Uytterhoeven wrote:
> > shouldn't they all just be that first one?  In other words, wouldn't it be
> > better to always provide the generic ioremap prototype and unify the ports
> > instead?
> 
> Agreed. But I'd go for the second one.

Eventually we should unify it and only have a single prototype.
But we have lots of implementations including inline functions, so
this will take a few more steps.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ