From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Adam Borowski <kilobyte@angband.pl>,
David Howells <dhowells@redhat.com>,
David Woodhouse <dwmw2@infradead.org>,
keyrings@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] certs: make system keyring depend on x509 parser
Date: Mon, 18 Jul 2022 08:55:35 +0200 [thread overview]
Message-ID: <0f226def-baf9-d6b2-2ee3-f6fae7d675f1@leemhuis.info> (raw)
In-Reply-To: <20220717231105.33005-1-kilobyte@angband.pl>
Hi, this is your Linux kernel regression tracker.
Thx for looking into this.
On 18.07.22 01:11, Adam Borowski wrote:
> This code requires x509_load_certificate_list() to be built-in.
>
> Fixes: 60050ffe3d770dd1df5b641aa48f49d07a54bd84
Just BTW: per docs.kernel.org/process/submitting-patches.html this
should be
Fixes: 60050ffe3d77 ("certs: Move load_certificate_list() to be with the
asymmetric keys code")
But I write for a different reason: Could you also please add "Link:"
and "Reported-by:" tags for earlier reports about this issue please:
Reported-by: kernel test robot <lkp@intel.com>
Link: https://lore.kernel.org/all/202206221515.DqpUuvbQ-lkp@intel.com/
Reported-by: Steven Rostedt <rostedt@goodmis.org>
Link:
https://lore.kernel.org/all/20220712104554.408dbf42@gandalf.local.home/
tia
> […]
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.
P.P.S.: Let me tell regzbot to monitor this thread:
#regzbot ^backmonitor:
https://lore.kernel.org/all/20220712104554.408dbf42@gandalf.local.home/
next prev parent reply other threads:[~2022-07-18 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 23:11 [PATCH] certs: make system keyring depend on x509 parser Adam Borowski
2022-07-18 6:55 ` Thorsten Leemhuis [this message]
2022-07-18 13:50 ` Adam Borowski
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=0f226def-baf9-d6b2-2ee3-f6fae7d675f1@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=keyrings@vger.kernel.org \
--cc=kilobyte@angband.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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).