($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: "Karel Balej" <balejk@matfyz.cz>
To: <regressions@lists.linux.dev>
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>,
	"Johannes Berg" <johannes@sipsolutions.net>,
	"James Prestwood" <prestwoj@gmail.com>,
	"Michael Yartys" <mail@yartys.no>
Subject: Re: [REGRESSION] Re: [PATCH] crypto: pkcs7: remove sha1 support
Date: Fri, 15 Mar 2024 14:09:01 +0100	[thread overview]
Message-ID: <CZUCJ4CEVXMS.2MML8IFVVTBC9@matfyz.cz> (raw)
In-Reply-To: <CZSVWO3IDZ96.38O0P161Z99XU@matfyz.cz>

#regzbot title: SHA1 support removal breaks iwd's ability to connect to eduroam
#regzbot monitor: https://lore.kernel.org/all/20240313233227.56391-1-ebiggers@kernel.org/
#regzbot monitor: https://lore.kernel.org/all/CZSHRUIJ4RKL.34T4EASV5DNJM@matfyz.cz/
#regzbot link: https://lore.kernel.org/iwd/njvxKaPo_CBxsQGaNSRHj8xOSxzk1_j_K-minIe4GCKUMB1qxJT8nPk9SGmfqg7Aepm_5dO7FEofYIYP1g15R9V5dJ0F8bN6O4VthSjzu1g=@yartys.no/

Sorry for the tracking mess...

      reply	other threads:[~2024-03-15 13:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CZSHRUIJ4RKL.34T4EASV5DNJM@matfyz.cz>
2024-03-13  8:56 ` [REGRESSION] Re: [PATCH] crypto: pkcs7: remove sha1 support 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
     [not found] ` <20231010212240.61637-1-dimitri.ledkov@canonical.com>
2024-03-13 19:54   ` Karel Balej
2024-03-15 13:09     ` Karel Balej [this message]

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=CZUCJ4CEVXMS.2MML8IFVVTBC9@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).