From: Randy Dunlap <rdunlap@infradead.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Build regressions/improvements in v6.6-rc1
Date: Tue, 12 Sep 2023 00:33:13 -0700 [thread overview]
Message-ID: <60faf0a3-a65c-ff83-6ecd-fe99ce9660f3@infradead.org> (raw)
In-Reply-To: <CAMuHMdUaXjDJ3=rPoUj3XD-fVXyfqQvohfn5FX=_21hOgGqeEg@mail.gmail.com>
On 9/11/23 23:49, Geert Uytterhoeven wrote:
> Hi Randy,
>
> On Tue, Sep 12, 2023 at 1:08 AM Randy Dunlap <rdunlap@infradead.org> wrote:
>> On 9/11/23 01:38, Geert Uytterhoeven wrote:
>>> 4 warning regressions:
>> []
>>> + modpost: WARNING: modpost: vmlinux: section mismatch in reference: ioremap_prot+0x88 (section: .text) -> ioremap_fixed (section: .init.text): => N/A
>>
>> I would consider trying to fix this one but I can't fathom trying to search thru 237 build logs with a web browser
>> to find which arch/config it is.
>>
>> I did start on that but I'm giving up.
>>
>> If possible, please add the arch/config info to the Build regressions/improvements reports
>> in the future.
>
> I always reply with more details after my analysis (which is a manual
> process). Unfortunately, due to hick-ups with vger and lore, none of
> the emails I sent out yesterday using git-send-email made it to the
> lists before last night, so I didn't have anything to reply to until
> this morning...
yep.
> Today, the email issues seem to have been fixed (although I still
> haven't received the report myself, but at least lore now has it),
> so the analysis is there.
I see it. Thanks.
> And FTR, I sent out a fix for the section mismatch yesterday, and
> Andrew has already picked it up.
:)
--
~Randy
next prev parent reply other threads:[~2023-09-12 7:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 23:53 Linux 6.6-rc1 Linus Torvalds
2023-09-11 2:38 ` linux-next: stats (Was: Linux 6.6-rc1) Stephen Rothwell
2023-09-11 9:02 ` Geert Uytterhoeven
2023-09-11 8:38 ` Build regressions/improvements in v6.6-rc1 Geert Uytterhoeven
2023-09-11 23:08 ` Randy Dunlap
2023-09-12 6:49 ` Geert Uytterhoeven
2023-09-12 7:33 ` Randy Dunlap [this message]
2023-09-12 6:39 ` Geert Uytterhoeven
2023-09-12 17:59 ` Linux 6.6-rc1 Guenter Roeck
2023-09-12 18:17 ` Linus Torvalds
2023-09-12 18:25 ` Helge Deller
2023-09-12 18:33 ` Guenter Roeck
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=60faf0a3-a65c-ff83-6ecd-fe99ce9660f3@infradead.org \
--to=rdunlap@infradead.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®