From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 5.18-rc3
Date: Sun, 17 Apr 2022 17:50:37 -0700 [thread overview]
Message-ID: <20220418005037.GA1094849@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wgBR6P8EseYMjfMjxQ_oTpoQmL0qvKpAw04kP-HBgSGFg@mail.gmail.com>
On Sun, Apr 17, 2022 at 02:19:01PM -0700, Linus Torvalds wrote:
> It's Sunday afternoon, and you all know what that means. It's time for
> another release candidate.
>
> (Yes, yes, it's also Easter Sunday, but priorities, people!)
>
> Things continue to look quite regular, although the diffstat may look
> a bit odd due to some email updates that ended up causing a lot of
> spread-out one-liner updates in the devicetree files.
>
> There's also a series to sound card probing error handling fixes ("Fix
> the missing snd_card_free() call at probe error") which ends up
> showing as a lot of few-lines across a number of sound drivers.
>
> But it all looks pretty small and fairly simple. Famous last words.
>
> Please do test,
Build results:
total: 151 pass: 150 fail: 1
Failed builds:
m68k:allmodconfig
Qemu test results:
total: 489 pass: 489 fail: 0
Building m68k:allmodconfig ... failed
--------------
Error log:
sound/oss/dmasound/dmasound_core.c:1431:12: error:
'dmasound_setup' defined but not used
Caused by commit 9dd7c46346ca ("sound/oss/dmasound: fix build when drivers
are mixed =y/=m"). Fixed with
https://vanko.io/project/alsa-devel/patch/20220414091940.2216-1-miles.chen@mediatek.com/
Guenter
next prev parent reply other threads:[~2022-04-18 0:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 21:19 Linus Torvalds
2022-04-18 0:50 ` Guenter Roeck [this message]
2022-04-19 7:20 ` Build regressions/improvements in v5.18-rc3 Geert Uytterhoeven
2022-04-19 7:26 ` Geert Uytterhoeven
2022-04-19 14:24 ` Randy Dunlap
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=20220418005037.GA1094849@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®