From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Mon, 11 May 2020 17:13:56 +0200 From: Christoph Hellwig Subject: Re: sort out the flush_icache_range mess Message-ID: <20200511151356.GB28634@lst.de> References: <20200510075510.987823-1-hch@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org To: Geert Uytterhoeven Cc: Christoph Hellwig , Andrew Morton , Arnd Bergmann , Roman Zippel , Linux-Arch , "open list:TENSILICA XTENSA PORT (xtensa)" , Michal Simek , Jessica Yu , "linux-ia64@vger.kernel.org" , linux-c6x-dev@linux-c6x.org, Linux-sh list , "open list:QUALCOMM HEXAGON..." , the arch/x86 maintainers , linux-um , Linux Kernel Mailing List , "open list:BROADCOM NVRAM DRIVER" , Linux MM , linux-m68k , Openrisc , alpha , sparclinux , Linux FS Devel , linux-riscv@lists.infradead.org, linuxppc-dev , Linux ARM List-ID: Message-ID: <20200511151356.5HQZbQ22tv1XKCWEFiz8YEW6v3zVxPurW4BZOf0Yj4k@z> On Mon, May 11, 2020 at 09:46:17AM +0200, Geert Uytterhoeven wrote: > Hi Christoph, > > On Sun, May 10, 2020 at 9:55 AM Christoph Hellwig wrote: > > none of which really are used by a typical MMU enabled kernel, as a.out can > > only be build for alpha and m68k to start with. > > Quoting myself: > "I think it's safe to assume no one still runs a.out binaries on m68k." > http://lore.kernel.org/r/CAMuHMdW+m0Q+j3rsQdMXnrEPm+XB5Y2AQrxW5sD1mZAKgmEqoA@mail.gmail.com Do you want to drop the: select HAVE_AOUT if MMU for m68k then? Note that we'll still need flush_icache_user_range for m68k with mmu, as it also allows binfmt_flat for mmu configs.