linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: Build regressions/improvements in v6.1-rc8
Date: Wed, 7 Dec 2022 16:11:28 +0100	[thread overview]
Message-ID: <CAMuHMdVxgfgbtdaFVzUWEmiJw13nQFkFG5SO_m4ixjYd=rsJow@mail.gmail.com> (raw)
In-Reply-To: <87cz8vmfh4.fsf@kernel.org>

Hi Kalle,

On Wed, Dec 7, 2022 at 3:54 PM Kalle Valo <kvalo@kernel.org> wrote:
> Geert Uytterhoeven <geert@linux-m68k.org> writes:
> > On Tue, 6 Dec 2022, Geert Uytterhoeven wrote:
> >> JFYI, when comparing v6.1-rc8[1] to v6.1-rc7[3], the summaries are:
> >>  - build errors: +1/-3
> >
> >   + /kisskb/src/drivers/net/wireless/cisco/airo.c: error: 'status_rid.currentXmitRate' is used uninitialized [-Werror=uninitialized]:  => 6152:45
> >
> > sh4-gcc11/sh-allmodconfig
> >
> > Looks like a real issue, albeit not new (but never seen before?).
>
> Weird, I can't find any recent change which would affect this function.
> So you have seen this warning only on v6.1-rc8?

The gcc11 build for sh4/allmodconfig was introduced quite recently on
kisskb, and it's still buggy (ICEs), so it's possible previous builds for that
target never went that far before...

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

      reply	other threads:[~2022-12-07 15:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-04 22:54 Linux 6.1-rc8 Linus Torvalds
2022-12-06  8:51 ` Build regressions/improvements in v6.1-rc8 Geert Uytterhoeven
2022-12-06  8:59   ` Geert Uytterhoeven
2022-12-07 14:54     ` Kalle Valo
2022-12-07 15:11       ` Geert Uytterhoeven [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='CAMuHMdVxgfgbtdaFVzUWEmiJw13nQFkFG5SO_m4ixjYd=rsJow@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@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).