[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200420113336.GA12078@alpha.franken.de>
Date: Mon, 20 Apr 2020 13:33:36 +0200
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Ralf Baechle <ralf@...ux-mips.org>,
James Hogan <jhogan@...nel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"kernelci.org bot" <bot@...nelci.org>,
Christoph Hellwig <hch@....de>
Subject: Re: linux-next: build failure after merge of the mips tree
On Mon, Apr 20, 2020 at 08:07:44PM +1000, Stephen Rothwell wrote:
> After merging the mips tree, today's linux-next build (mips gpr_defconfig)
> failed like this:
>
> arch/mips/alchemy/common/setup.c:99:9: error: implicit declaration of function ‘remap_pfn_range’; did you mean ‘io_remap_pfn_range’? [-Werror=implicit-function-declaration]
>
> Caused by commit
>
> d399157283fb ("MIPS: cleanup fixup_bigphys_addr handling")
I've pushed a fix to mips-next branch.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
Powered by blists - more mailing lists