From: Herbert Xu <herbert@gondor.apana.org.au>
To: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
Cc: Jim Quigley <Jim.Quigley@oracle.com>,
Matt Mackall <mpm@selenic.com>,
"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@vger.kernel.org>
Subject: Re: virtio:rng: Virtio RNG devices need to be re-registered after suspend/resume
Date: Tue, 7 Nov 2017 11:36:44 +0800 [thread overview]
Message-ID: <20171107033643.GA19846@gondor.apana.org.au> (raw)
In-Reply-To: <CANc+2y7JzcobX7wj236SD4FcimWkqBnprY1Ew7FUprOijn8U-w@mail.gmail.com>
On Tue, Nov 07, 2017 at 08:44:17AM +0530, PrasannaKumar Muralidharan wrote:
> Hi Herbert,
>
> On 6 November 2017 at 12:39, Herbert Xu <herbert@gondor.apana.org.au> wrote:
> > On Fri, Nov 03, 2017 at 09:57:21AM +0000, Jim Quigley wrote:
> >> moved the call to hwrng_register() out of the probe routine into the scan
> >> routine. We need to call hwrng_register() after a suspend/restore cycle
> >> to re-register the device, but the scan function is not invoked for the
> >> restore. Add the call to hwrng_register() to virtio_restore().
> >
> > Patch applied. Thanks.
>
> My rb tag is missing in the commit.
That's because you didn't start it on a new line.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2017-11-07 3:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 9:57 virtio:rng: Virtio RNG devices need to be re-registered after suspend/resume Jim Quigley
2017-11-03 13:06 ` PrasannaKumar Muralidharan
2017-11-03 14:41 ` Jim Quigley
[not found] ` <CANc+2y4cEAHudxdK6Y0TbskGMH6jpLg0cfWt77JR44fzYU94HA@mail.gmail.com>
2017-11-03 15:25 ` Fwd: " PrasannaKumar Muralidharan
2017-11-03 15:33 ` PrasannaKumar Muralidharan
2017-11-03 15:36 ` PrasannaKumar Muralidharan
2017-11-06 7:09 ` Herbert Xu
2017-11-07 3:14 ` PrasannaKumar Muralidharan
2017-11-07 3:36 ` Herbert Xu [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=20171107033643.GA19846@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=Jim.Quigley@oracle.com \
--cc=linux-crypto@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=prasannatsmkumar@gmail.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