From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
sparclinux@vger.kernel.org, linux-um@lists.infradead.org,
Lakshmi Sowjanya D <lakshmi.sowjanya.d@intel.com>,
kvm@vger.kernel.org, linux-mips@vger.kernel.org,
"Tobin C. Harding" <me@tobin.cc>,
alsa-devel@alsa-project.org, amd-gfx@lists.freedesktop.org,
netdev@vger.kernel.org
Subject: Re: Build regressions/improvements in v5.17-rc1
Date: Tue, 25 Jan 2022 15:20:02 +0100 [thread overview]
Message-ID: <20220125142002.GA26778@alpha.franken.de> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2201240851560.2674757@ramsan.of.borg>
On Mon, Jan 24, 2022 at 08:55:40AM +0100, Geert Uytterhoeven wrote:
> > + /kisskb/src/lib/test_printf.c: error: "PTR" redefined [-Werror]: => 247:0, 247
> > + /kisskb/src/sound/pci/ca0106/ca0106.h: error: "PTR" redefined [-Werror]: => 62, 62:0
>
> mips-gcc8/mips-allmodconfig
> mipsel/mips-allmodconfig
fixing patch sent.
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:[~2022-01-25 14:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220123125737.2658758-1-geert@linux-m68k.org>
2022-01-24 7:55 ` Build regressions/improvements in v5.17-rc1 Geert Uytterhoeven
2022-01-24 17:04 ` Jakub Kicinski
2022-01-24 17:23 ` Jakub Kicinski
2022-01-24 18:51 ` Alex Deucher
2022-01-24 18:55 ` Geert Uytterhoeven
2022-01-24 19:11 ` Randy Dunlap
2022-01-25 1:23 ` Felix Kuehling
2022-01-25 1:29 ` Randy Dunlap
2022-01-25 12:56 ` D, Lakshmi Sowjanya
2022-01-25 14:20 ` 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=20220125142002.GA26778@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=alsa-devel@alsa-project.org \
--cc=amd-gfx@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=kvm@vger.kernel.org \
--cc=lakshmi.sowjanya.d@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=me@tobin.cc \
--cc=netdev@vger.kernel.org \
--cc=sparclinux@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).