From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: David Howells <dhowells@redhat.com>
Cc: dhowells@redhat.com, Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Tianjia Zhang <tianjia.zhang@linux.alibaba.com>,
Gilad Ben-Yossef <gilad@benyossef.com>,
keyrings@vger.kernel.org, linux-crypto@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] crypto: public_key: check that pkey_algo is non-NULL before passing it to strcmp()
Date: Mon, 18 Jan 2021 18:13:02 +0100 [thread overview]
Message-ID: <87sg6yqich.fsf@toke.dk> (raw)
In-Reply-To: <2656681.1610542679@warthog.procyon.org.uk>
David Howells <dhowells@redhat.com> writes:
> Toke Høiland-Jørgensen <toke@redhat.com> wrote:
>
>> Reviewed-by: Toke Høiland-Jørgensen <toke@redhat.com>
>>
>> and also, if you like:
>>
>> Tested-by: Toke Høiland-Jørgensen <toke@redhat.com>
>
> Thanks!
Any chance of that patch getting into -stable anytime soon? Would be
nice to have working WiFi without having to compile my own kernels ;)
-Toke
next prev parent reply other threads:[~2021-01-18 17:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 16:10 [PATCH] crypto: public_key: check that pkey_algo is non-NULL before passing it to strcmp() Toke Høiland-Jørgensen
2021-01-13 2:39 ` Tianjia Zhang
2021-01-13 11:29 ` Toke Høiland-Jørgensen
2021-01-13 11:11 ` David Howells
2021-01-13 11:36 ` Toke Høiland-Jørgensen
2021-01-13 12:57 ` David Howells
2021-01-18 17:13 ` Toke Høiland-Jørgensen [this message]
2021-01-18 21:09 ` João Fonseca
2021-01-21 5:58 ` Tee Hao Wei
2021-03-10 12:02 ` Greg KH
2021-03-15 10:52 ` Toke Høiland-Jørgensen
2021-03-15 12:07 ` Greg KH
2021-01-14 2:55 ` Jarkko Sakkinen
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=87sg6yqich.fsf@toke.dk \
--to=toke@redhat.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=gilad@benyossef.com \
--cc=herbert@gondor.apana.org.au \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tianjia.zhang@linux.alibaba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.