From: Thomas Bogendoerfer <tsbogend@alpha•franken.de>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Ralf Baechle <ralf@linux-mips•org>,
James Hogan <jhogan@kernel•org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
"kernelci.org bot" <bot@kernelci•org>,
Christoph Hellwig <hch@lst•de>
Subject: Re: linux-next: build failure after merge of the mips tree
Date: Mon, 20 Apr 2020 13:33:36 +0200 [thread overview]
Message-ID: <20200420113336.GA12078@alpha.franken.de> (raw)
In-Reply-To: <20200420200744.620c2782@canb.auug.org.au>
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 ]
next prev parent reply other threads:[~2020-04-20 11:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 10:07 linux-next: build failure after merge of the mips tree Stephen Rothwell
2020-04-20 11:33 ` Thomas Bogendoerfer [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-27 5:12 Stephen Rothwell
2023-03-27 8:41 ` Thomas Bogendoerfer
2013-10-07 15:18 linux-next: Tree for Oct 7 Thierry Reding
2013-10-07 15:18 ` linux-next: build failure after merge of the mips tree Thierry Reding
2013-02-17 23:43 Stephen Rothwell
2013-02-17 23:59 ` Hauke Mehrtens
2013-02-20 0:29 ` Stephen Rothwell
2011-11-10 1:22 Stephen Rothwell
2010-07-27 1:14 Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200420113336.GA12078@alpha.franken.de \
--to=tsbogend@alpha$(echo .)franken.de \
--cc=bot@kernelci$(echo .)org \
--cc=hch@lst$(echo .)de \
--cc=jhogan@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=ralf@linux-mips$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox