linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 5.15
Date: Mon, 1 Nov 2021 16:19:49 +0000	[thread overview]
Message-ID: <YYATpRgJHditIHZT@google.com> (raw)
In-Reply-To: <CAHp75Vef8QW3Y0yA702KUqPDHNRLN0kCv06=cgPpgPbUeAb-dw@mail.gmail.com>

On Mon, 01 Nov 2021, Andy Shevchenko wrote:

> On Sun, Oct 31, 2021 at 11:09 PM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > It's been calm, and I have no excuse to add an extra rc, so here we
> > are, with v5.15 pushed out, and the merge window starting tomorrow.
> >
> > Which is going to be a bit inconvenient for me, since I also have some
> > conference travel coming up. But it's only a couple of days and I'll
> > have my laptop with me. Sometimes the release timing works out, and
> > sometimes it doesn't..
> >
> > Anyway, the last week of 5.15 was mainly networking and gpu fixes,
> > with some random sprinkling of other things (a few btrfs reverts, some
> > kvm updates, minor other fixes here and there - a few architecture
> > fixes, couple of tracing, small driver fixes etc). Full shortlog
> > appended.
> >
> > This release may have started out with some -Werror pain, but it
> > calmed down fairly quickly and on the whole 5.15 was fair small and
> > calm. Let's hope for more of the same - without Werror issues this
> > time - for the upcoming merge window.
> 
> Do we really now have any use of COMPILE_TEST=y WERROR=y with `make W=1`?
> To me it seems every CI just disabled it because it's impossible to
> build a kernel anymore.
> 
> What is the roadmap of fixing this (to some extent)?
> 
> I remember that Lee spent a lot of time cleaning up W=1 cases. Maybe
> he knows the state of affairs of this with -Werror enabled...

Probably never.  I managed to get the warnings down from ~18k to ~2k
IIRC.  However subsystems like GPU keep adding 10's of them every
release, so the job became perpetual.

I do plan on doing another rotation once I get a bit more free time.

-- 
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2021-11-01 16:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-31 21:09 Linus Torvalds
2021-11-01  0:23 ` Guenter Roeck
2021-11-01  8:13   ` Geert Uytterhoeven
2021-11-02  1:17     ` Guenter Roeck
2021-11-02  1:44       ` Linus Torvalds
2021-11-02  3:19         ` Guenter Roeck
2021-11-01  4:49 ` Thorsten is tracking regression again and could need a little help (was: Re: Linux 5.15) Thorsten Leemhuis
     [not found]   ` <c11d94b4-1701-4e26-efd1-42038342c4aa@kaputniks.org>
2021-11-01 11:56     ` Greg KH
2021-11-01 12:54     ` Thorsten Leemhuis
2021-11-01 12:33   ` Greg KH
2021-11-01 12:44     ` Thorsten Leemhuis
2021-11-01 13:03       ` Greg KH
2021-11-01 13:34         ` Thorsten Leemhuis
2021-11-01 15:27           ` Greg KH
2021-11-01 16:19             ` Thorsten Leemhuis
2021-11-01 15:07 ` Linux 5.15 Andy Shevchenko
2021-11-01 16:19   ` Lee Jones [this message]
2021-11-01 17:25 ` Sudip Mukherjee

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=YYATpRgJHditIHZT@google.com \
    --to=lee.jones@linaro.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: Linux 5.15' \
    /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

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).