From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Arnd Bergmann <arnd@arndb.de>,
Viresh Kumar <viresh.kumar@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 5.15-rc3
Date: Thu, 30 Sep 2021 06:42:59 -0700 [thread overview]
Message-ID: <20210930134259.GA521118@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wgdZgiLoHoQS+C2CP8x5PGn6b=GBkY6K9T3QhDoaeV9mg@mail.gmail.com>
On Mon, Sep 27, 2021 at 01:46:42PM -0700, Linus Torvalds wrote:
> On Mon, Sep 27, 2021 at 1:35 PM Thomas Bogendoerfer
> <tsbogend@alpha.franken.de> wrote:
> >
> > if it was a fix in the mips tree I would have sent it already, but it's
> > watchdog driver fix, which was meant to be picked up by Wim.
>
> Oh, my bad. Regardless, it's fixed in my tree now, and all of
> Guenter's build failures should be fixed.
>
Sorry for not getting back earlier; I have limited internet access
right now.
I _am_ watchdog co-maintainer, so I guess it is partially my fault.
Wim normally handles pull requests. I had asked him to send a pull
request with this patch, but unfortunately he didn't reply.
> Of course, other random configs and compilers are still an issue, but
> it's nice to see that most (all?) architectures can at least do a
> clean "allmodconfig" build for some random set of tools. I don't think
> we've ever been there before.
Not all of them, but that is nothing news and unrelated to -Werror.
Many 'minor' architectures do not and never did successfully build
allmodconfig, and others (nds32) need a specific gcc/binutils version
to build it. I submitted a set of patches for csky to enable it to build
allmodconfig with upstream gcc, so maybe we'll get that in 5.16. For
others it may be a lost cause. I can create a list with build errors
if there is interest.
Guenter
next prev parent reply other threads:[~2021-09-30 13:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 21:21 Linux 5.15-rc3 Linus Torvalds
2021-09-27 11:05 ` Guenter Roeck
2021-09-27 18:55 ` Linus Torvalds
2021-09-27 20:09 ` Thomas Bogendoerfer
2021-09-27 20:46 ` Linus Torvalds
2021-09-30 13:42 ` Guenter Roeck [this message]
2021-09-27 22:31 ` Michael S. Tsirkin
2021-09-27 20:48 Sedat Dilek
2021-09-27 21:47 ` Jason Gunthorpe
2021-09-27 21:48 ` Nick Desaulniers
2021-09-27 21:49 ` Sedat Dilek
2021-10-01 15:44 ` Sedat Dilek
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=20210930134259.GA521118@roeck-us.net \
--to=linux@roeck-us.net \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=tsbogend@alpha.franken.de \
--cc=viresh.kumar@linaro.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).