From: "Keith Packard" <keithp@keithp.com>
To: Tom Lendacky <thomas.lendacky@amd.com>, linux-kernel@vger.kernel.org
Cc: Matt Mackall <mpm@selenic.com>, Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [PATCH] hwrng: Explicitly drop current_rng when unregistering rng device
Date: Sun, 04 Feb 2018 16:08:57 -0800 [thread overview]
Message-ID: <87shag1ena.fsf@keithp.com> (raw)
In-Reply-To: <3f489790-dbfd-e726-e957-7bc7af0745bb@amd.com>
[-- Attachment #1: Type: text/plain, Size: 372 bytes --]
Tom Lendacky <thomas.lendacky@amd.com> writes:
> A similar fix was already in the cryptodev tree and I thought was part of
> a recent pull request.
Yup, just saw it on master. I've checked and it will do pretty much the
same thing as my patch, with the addition of clearing
cur_rng_set_by_user, which is necessary. Thanks for looking at my patch!
--
-keith
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2018-02-05 0:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 23:26 [PATCH] hwrng: Explicitly drop current_rng when unregistering rng device Keith Packard
2018-01-31 14:36 ` Tom Lendacky
2018-02-05 0:08 ` Keith Packard [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=87shag1ena.fsf@keithp.com \
--to=keithp@keithp.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=thomas.lendacky@amd.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 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).