From: "Karel Balej" <balejk@matfyz.cz>
To: "Johannes Berg" <johannes@sipsolutions.net>,
"James Prestwood" <prestwoj@gmail.com>,
"Michael Yartys" <mail@yartys.no>
Cc: <alexandre.torgue@foss.st.com>, <davem@davemloft.net>,
<dhowells@redhat.com>, <herbert@gondor.apana.org.au>,
<keyrings@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-modules@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>, <mcgrof@kernel.org>,
<mcoquelin.stm32@gmail.com>, <linux-wireless@vger.kernel.org>,
<netdev@vger.kernel.org>, <dimitri.ledkov@canonical.com>,
<iwd@lists.linux.dev>, <regressions@lists.linux.dev>
Subject: Re: [REGRESSION] Re: [PATCH] crypto: pkcs7: remove sha1 support
Date: Wed, 13 Mar 2024 20:54:44 +0100 [thread overview]
Message-ID: <CZSVWO3IDZ96.38O0P161Z99XU@matfyz.cz> (raw)
In-Reply-To: <CZSHRUIJ4RKL.34T4EASV5DNJM@matfyz.cz>
Thank you all for your feedback so far.
Since it seems that this really is a regression on the kernel side, let
me add the appropriate list to Cc and tag this:
#regzbot introduced: 16ab7cb5825f
Best regards,
K. B.
next prev parent reply other threads:[~2024-03-13 19:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231010212240.61637-1-dimitri.ledkov@canonical.com>
2024-03-13 8:50 ` [REGRESSION] Re: [PATCH] crypto: pkcs7: remove sha1 support Karel Balej
2024-03-13 8:56 ` Johannes Berg
2024-03-13 17:26 ` James Prestwood
2024-03-13 19:44 ` Eric Biggers
2024-03-13 20:12 ` James Prestwood
2024-03-13 20:22 ` Eric Biggers
2024-03-13 21:17 ` James Prestwood
2024-03-13 22:10 ` Eric Biggers
2024-03-13 22:51 ` Jeff Johnson
2024-03-13 23:06 ` Eric Biggers
2024-03-13 23:40 ` Eric Biggers
2024-03-14 11:52 ` James Prestwood
2024-03-14 12:22 ` James Bottomley
2024-03-14 20:20 ` Eric Biggers
2024-03-14 23:38 ` Ard Biesheuvel
2024-03-13 18:39 ` Michael Yartys
2024-03-13 19:54 ` Karel Balej [this message]
2024-03-15 13:09 ` Karel Balej
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=CZSVWO3IDZ96.38O0P161Z99XU@matfyz.cz \
--to=balejk@matfyz.cz \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=dimitri.ledkov@canonical.com \
--cc=herbert@gondor.apana.org.au \
--cc=iwd@lists.linux.dev \
--cc=johannes@sipsolutions.net \
--cc=keyrings@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mail@yartys.no \
--cc=mcgrof@kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=prestwoj@gmail.com \
--cc=regressions@lists.linux.dev \
/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