From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: Linux 6.4-rc1
Date: Mon, 8 May 2023 13:34:30 -0700 [thread overview]
Message-ID: <3b2e90bb-c28f-447a-abf8-2b5453da8092@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wiUxm-NZ1si8dXWVTTJ9n3c+1SRTC0V+Lk7hOE4bDVwJQ@mail.gmail.com>
On Sun, May 07, 2023 at 02:18:22PM -0700, Linus Torvalds wrote:
> So here we are, two weeks later, with the merge window over, and -rc1
> tagged and pushed out.
>
[ ... ]
>
> Anyway, please do go test it all out,
>
Build results:
total: 152 pass: 146 fail: 6
Failed builds:
arm:allmodconfig
i386:allyesconfig
i386:allmodconfig
mips:allmodconfig
powerpc:ppc32_allmodconfig
xtensa:allmodconfig
Qemu test results:
total: 520 pass: 520 fail: 0
The build failure is
drivers/media/platform/nxp/imx8-isi/imx8-isi-hw.c:
In function 'mxc_isi_channel_set_inbuf':
drivers/media/platform/nxp/imx8-isi/imx8-isi-hw.c:33:5: error:
"CONFIG_ARCH_DMA_ADDR_T_64BIT" is not defined, evaluates to 0
The problem has been fixed in -next since April 18 with commit 9829ed20b019
("media: nxp: imx8-isi: fix buiding on 32-bit"). Hopefully that commit
should find its way into mainline in the near future.
Guenter
next prev parent reply other threads:[~2023-05-08 20:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-07 21:18 Linus Torvalds
2023-05-08 11:57 ` Build regressions/improvements in v6.4-rc1 Geert Uytterhoeven
2023-05-08 12:14 ` Geert Uytterhoeven
2023-05-08 15:19 ` Pratyush Yadav
2023-05-08 15:32 ` Geert Uytterhoeven
2023-05-08 15:46 ` Raghavendra, Vignesh
2023-05-09 19:25 ` [PATCH 1/2] mtd: spi-nor: spansion: make sure local struct does not contain garbage Tudor Ambarus
2023-05-09 19:25 ` [PATCH 2/2] " Tudor Ambarus
2023-05-09 19:30 ` Tudor Ambarus
2023-05-09 19:39 ` [PATCH v2] " Tudor Ambarus
2023-05-17 7:17 ` Tudor Ambarus
2023-05-22 15:58 ` Miquel Raynal
2023-05-08 20:34 ` Guenter Roeck [this message]
2023-05-10 4:31 ` linux-next stats (Was: Linux 6.4-rc1) Stephen Rothwell
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=3b2e90bb-c28f-447a-abf8-2b5453da8092@roeck-us.net \
--to=linux@roeck-us.net \
--cc=arnd@arndb.de \
--cc=hverkuil-cisco@xs4all.nl \
--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®