From: Thorsten Leemhuis <regressions@leemhuis.info>
To: regressions@lists.linux.dev, Guenter Roeck <linux@roeck-us.net>
Cc: linux-alpha@vger.kernel.org, kernel test robot <lkp@intel.com>,
Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH] alpha: Use generic <asm-generic/io.h> #forregzbot
Date: Thu, 13 Oct 2022 14:36:47 +0200 [thread overview]
Message-ID: <3c7c22f1-2e9d-8bdc-33b7-eb8dcb8a3593@leemhuis.info> (raw)
In-Reply-To: <e99d33ff-4bfe-4727-a5ca-f4987b871ccd@app.fastmail.com>
[Note: this mail is primarily send for documentation purposes and/or for
regzbot, my Linux kernel regression tracking bot. That's why I removed
most or all folks from the list of recipients, but left any that looked
like a mailing lists. These mails usually contain '#forregzbot' in the
subject, to make them easy to spot and filter out.]
On 12.10.22 17:32, Arnd Bergmann wrote:
> On Wed, Oct 12, 2022, at 4:05 PM, Guenter Roeck wrote:
>> On Tue, Oct 04, 2022 at 10:28:24PM +0200, Arnd Bergmann wrote:
>> Unfortunately that did not completely fix the problem, or maybe the fix got
>> lost. In mainline, when building alpha:allnoconfig:
>>
>> arch/alpha/kernel/core_marvel.c:807:1: error: expected '=', ',', ';',
>> 'asm' or '__attribute__' before 'marvel_ioread8'
>> 807 | marvel_ioread8(const void __iomem *xaddr)
>>
>> The code is:
>>
>> unsigned u8
>> marvel_ioread8(const void __iomem *xaddr)
>>
>> The compiler doesn't like "unsigned u8".
>
> Right, I fixed up a different bug and introduced this wrong type.
> I didn't catch my mistake until after the pull request was
> merged, but fixed it in
>
> https://git.kernel.org/pub/scm/linux/kernel/git/arnd/asm-generic.git/commit/?id=2e21c1575208
>
> which should be in linux-next. I was giving it a little more
> time to be see if there are any other regressions I caused.
In that case:
#regzbot fixed-by: 2e21c157520
Ciao, Thorsten
prev parent reply other threads:[~2022-10-13 12:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 9:20 [PATCH] alpha: Use generic <asm-generic/io.h> Linus Walleij
2022-08-18 10:28 ` Arnd Bergmann
2022-09-05 19:30 ` Linus Walleij
2022-09-05 20:52 ` Arnd Bergmann
2022-09-06 14:59 ` Matt Turner
2022-10-02 22:45 ` Guenter Roeck
2022-10-03 13:03 ` Arnd Bergmann
2022-10-03 15:07 ` Guenter Roeck
2022-10-03 18:49 ` Linus Walleij
2022-10-04 19:42 ` Guenter Roeck
2022-10-04 20:28 ` Arnd Bergmann
2022-10-12 14:05 ` Guenter Roeck
2022-10-12 15:32 ` Arnd Bergmann
2022-10-13 12:36 ` Thorsten Leemhuis [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=3c7c22f1-2e9d-8bdc-33b7-eb8dcb8a3593@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkp@intel.com \
--cc=regressions@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).