From: Arnd Bergmann <arnd@arndb.de>
To: Hugo Lefeuvre <hle@owl.eu.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the asm-generic tree
Date: Tue, 19 Feb 2019 11:14:44 +0100 [thread overview]
Message-ID: <CAK8P3a0omA-__7MLAw_SKuug_GZ0FfFPVr1Tsnx5Hb0sesv8gw@mail.gmail.com> (raw)
In-Reply-To: <20190219074519.GA2294@behemoth.owl.eu.com.local>
On Tue, Feb 19, 2019 at 8:45 AM Hugo Lefeuvre <hle@owl.eu.com> wrote:
>
> Hi Stephen, Arnd,
>
> > After merging the asm-generic tree, today's linux-next build (powerpc
> > allnoconfig) failed like this:
> > ...
> > Caused by commit
> >
> > 8e074c243ed3 ("iomap: add missing const to ioread*/iowrite addr arg")
>
> I have prepared a patch addressing this issue, and am currently building it
> with a powerpc cross compiler. I'll submit it once it's done. Please tell
> me if I should update the initial patch instead.
>
> > The const qualifiers are also missing in:
> >
> > arch/parisc/lib/iomap.c
> > arch/sh/kernel/iomap.c
>
> I also have patches for these architectures, but it is more complicated for
> me to test them with a cross compiler. Should I still submit them?
I'm not sending a pull request for this if it breaks any architectures,
so I think we need to fix them all, and I suppose we also have to
change all architectures in the same patch that changes the architecture
independent declaration, so it doesn't break intermittently.
At this point, I'd probably drop your patches from my asm-generic
tree entirely to avoid the regression, and wait for you to resend
them all after 5.1-rc1, for inclusion in 5.2.
Can you elaborate on the original problem that you saw? Maybe
we can have a different workaround for it in the meantime.
Arnd
next prev parent reply other threads:[~2019-02-19 10:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 6:36 Stephen Rothwell
2019-02-19 7:45 ` Hugo Lefeuvre
2019-02-19 10:14 ` Arnd Bergmann [this message]
2019-02-19 11:19 ` Hugo Lefeuvre
2019-02-19 14:42 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2026-11-13 15:04 Mark Brown
2026-11-13 15:45 ` Thomas Huth
2026-11-13 16:16 ` Arnd Bergmann
2026-11-16 9:55 ` Thomas Huth
2026-11-16 9:59 ` Arnd Bergmann
2024-08-06 4:54 Stephen Rothwell
2024-08-06 6:30 ` Arnd Bergmann
2024-08-06 6:50 ` Stephen Rothwell
2022-07-20 12:36 Stephen Rothwell
2022-07-20 12:51 ` Arnd Bergmann
2022-07-21 6:57 ` Lukas Bulwahn
2018-03-15 22:13 Stephen Rothwell
2018-03-15 22:47 ` Bin Liu
2018-03-16 8:07 ` Arnd Bergmann
2015-10-14 22:55 Stephen Rothwell
2015-10-14 23:32 ` kbuild test robot
2015-10-15 2:37 ` Stephen Rothwell
2014-11-19 7:54 Stephen Rothwell
2014-11-19 9:21 ` Arnd Bergmann
2014-09-26 10:02 Stephen Rothwell
2014-09-26 10:53 ` Will Deacon
2014-09-26 11:14 ` Arnd Bergmann
2014-09-29 22:31 ` Stephen Rothwell
2014-09-30 10:00 ` Arnd Bergmann
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=CAK8P3a0omA-__7MLAw_SKuug_GZ0FfFPVr1Tsnx5Hb0sesv8gw@mail.gmail.com \
--to=arnd@arndb.de \
--cc=hle@owl.eu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®