From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"D. Wythe" <alibuda@linux.alibaba.com>,
bpf@vger.kernel.org,
Alexandre Chartre <alexandre.chartre@oracle.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Subject: Re: Linux 6.19-rc1
Date: Mon, 15 Dec 2025 18:16:59 +0100 [thread overview]
Message-ID: <aUBCi_MPt5rHSXqs@alpha.franken.de> (raw)
In-Reply-To: <516deeb7-102d-42ae-b925-64bba6281f14@roeck-us.net>
On Mon, Dec 15, 2025 at 06:46:29AM -0800, Guenter Roeck wrote:
> -----------------------------------------
> Building mips:db1xxx_defconfig ... failed
> Building mips:mtx1_defconfig ... failed
>
> --------------
> Error log:
> In file included from include/linux/pgtable.h:6,
> from include/linux/mm.h:31,
> from arch/mips/alchemy/common/setup.c:30:
> arch/mips/include/asm/pgtable.h:608:32: error: static declaration of 'io_remap_pfn_range_pfn' follows non-static declaration
> 608 | #define io_remap_pfn_range_pfn io_remap_pfn_range_pfn
> | ^~~~~~~~~~~~~~~~~~~~~~
> arch/mips/alchemy/common/setup.c:97:29: note: in expansion of macro 'io_remap_pfn_range_pfn'
> 97 | static inline unsigned long io_remap_pfn_range_pfn(unsigned long pfn,
> | ^~~~~~~~~~~~~~~~~~~~~~
> arch/mips/include/asm/pgtable.h:607:15: note: previous declaration of 'io_remap_pfn_range_pfn' with type 'long unsigned int(long unsigned int, long unsigned int)'
> 607 | unsigned long io_remap_pfn_range_pfn(unsigned long pfn, unsigned long size);
> | ^~~~~~~~~~~~~~~~~~~~~~
>
> Probably caused by commit c707a68f9468 ("mm: abstract io_remap_pfn_range()
> based on PFN") or related patches. Still bisecting.
I've applied to patch to mips-fixes branch for that.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2025-12-15 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHk-=wgizos80st3bL3EoEoh0+07u9zRjsw45M+RS-js-bcwag@mail.gmail.com>
2025-12-15 14:46 ` Linux 6.19-rc1 Guenter Roeck
2025-12-15 16:23 ` Alexei Starovoitov
2025-12-15 17:16 ` Thomas Bogendoerfer [this message]
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=aUBCi_MPt5rHSXqs@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=alexandre.chartre@oracle.com \
--cc=alibuda@linux.alibaba.com \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lorenzo.stoakes@oracle.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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