From: Eric DeVolder <eric.devolder@oracle.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Jul 10 (arch/s390/kernel/machine_kexec_file.c)
Date: Mon, 10 Jul 2023 15:23:49 -0500 [thread overview]
Message-ID: <8a848504-6e4c-ba7a-4777-3175c1fdc6d7@oracle.com> (raw)
In-Reply-To: <9536c8ca-a0f2-c4be-d705-2ac1054ebf7d@infradead.org>
On 7/10/23 15:11, Randy Dunlap wrote:
>
>
> On 7/9/23 18:38, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20230707:
>>
>
> on s390:
>
> ../arch/s390/kernel/machine_kexec_file.c: In function 's390_verify_sig':
> ../arch/s390/kernel/machine_kexec_file.c:69:15: error: implicit declaration of function 'verify_pkcs7_signature' [-Werror=implicit-function-declaration]
> 69 | ret = verify_pkcs7_signature(kernel, kernel_len,
> | ^~~~~~~~~~~~~~~~~~~~~~
> cc1: some warnings being treated as errors
>
>
> Full randconfig file is attached.
>
Randy,
Thanks for this. This appears to be randconfig testing against linux-next.
As of right now, linux-next does not contain the v5 that I posted friday.
The v5 posted friday was picked up by Andrew and over the weekend no fails
discovered, and the series currently sits in mm-everything branch. So hopefully
it will appear soon in linux-next!
Let me know if I misunderstand the situation.
Thanks!
eric
next prev parent reply other threads:[~2023-07-10 20:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 1:38 linux-next: Tree for Jul 10 Stephen Rothwell
2023-07-10 20:11 ` linux-next: Tree for Jul 10 (arch/s390/kernel/machine_kexec_file.c) Randy Dunlap
2023-07-10 20:23 ` Eric DeVolder [this message]
2023-07-10 21:27 ` Eric DeVolder
2023-07-10 22:15 ` Randy Dunlap
2023-07-11 18:49 ` Eric DeVolder
2023-07-12 15:18 ` Eric DeVolder
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=8a848504-6e4c-ba7a-4777-3175c1fdc6d7@oracle.com \
--to=eric.devolder@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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