From: Joel Fernandes <joel@joelfernandes.org>
To: Yu Kuai <yukuai3@huawei.com>
Cc: stable <stable@vger.kernel.org>, Guenter Roeck <linux@roeck-us.net>
Subject: Re: Build failures / crashes in stable queue branches
Date: Sat, 15 Jul 2023 15:49:23 +0000 [thread overview]
Message-ID: <20230715154923.GA2193946@google.com> (raw)
In-Reply-To: <897ebb05-5a1f-e353-8877-49721c52d065@roeck-us.net>
Hi Yu,
On Fri, Jul 14, 2023 at 03:21:46AM -0700, Guenter Roeck wrote:
[..]
> ---------
> 6.1.y:
>
> Build reference: v6.1.38-393-gb6386e7314b4
> Compiler version: alpha-linux-gcc (GCC) 11.4.0
> Assembler version: GNU assembler (GNU Binutils) 2.40
>
> Building alpha:allmodconfig ... failed
> Building m68k:allmodconfig ... failed
> --------------
> Error log:
> <stdin>:1517:2: warning: #warning syscall clone3 not implemented [-Wcpp]
> In file included from block/genhd.c:28:
> block/genhd.c: In function 'disk_release':
> include/linux/blktrace_api.h:88:57: error: statement with no effect [-Werror=unused-value]
> 88 | # define blk_trace_remove(q) (-ENOTTY)
> | ^
> block/genhd.c:1185:9: note: in expansion of macro 'blk_trace_remove'
> 1185 | blk_trace_remove(disk->queue);
6.1 stable is broken and gives build warning without:
cbe7cff4a76b ("blktrace: use inline function for blk_trace_remove() while blktrace is disabled")
Could you please submit it to stable for 6.1? (I could have done that but it
looks like you already backported related patches so its best for you to do
it, thanks for your help!).
thanks,
- Joel
next prev parent reply other threads:[~2023-07-15 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 10:21 Build failures / crashes in stable queue branches Guenter Roeck
2023-07-15 15:49 ` Joel Fernandes [this message]
2023-07-16 3:20 ` Yu Kuai
2023-07-16 14:30 ` Greg KH
2023-07-18 13:52 ` Joel Fernandes
2023-07-18 14:44 ` Greg KH
2023-07-18 17:14 ` Joel Fernandes
2023-07-19 1:16 ` Yu Kuai
2023-07-19 1:51 ` Joel Fernandes
2023-07-16 14:30 ` Greg KH
2023-07-16 14:35 ` Greg KH
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=20230715154923.GA2193946@google.com \
--to=joel@joelfernandes.org \
--cc=linux@roeck-us.net \
--cc=stable@vger.kernel.org \
--cc=yukuai3@huawei.com \
/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