From: jgg@ziepe.ca (Jason Gunthorpe)
To: linux-security-module@vger.kernel.org
Subject: [PATCH v2] tpm: Move Linux RNG connection to hwrng
Date: Tue, 7 Nov 2017 09:04:04 -0700 [thread overview]
Message-ID: <20171107160404.GG21466@ziepe.ca> (raw)
In-Reply-To: <CANc+2y6dx_2zOzFA5aFs7RpEV8aNqxpDghmx+q_+XyendYJoew@mail.gmail.com>
On Tue, Nov 07, 2017 at 08:50:44AM +0530, PrasannaKumar Muralidharan wrote:
> I am assuming you are talking about the following patches - using
> struct tpm_chip instead of chip number and this patch.
yes
> I won't be able to test if struct tpm_chip usage as I don't have
> multiple tpm hw in one machine. In case of tpm rng changes I can test
> only the lifecycle of tpm rng device. Is that enough? I feel my test
> will be limited. Please provide your thoughts on this.
That is certainly better than no testing.
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-11-07 16:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 20:05 [PATCH v2] tpm: Move Linux RNG connection to hwrng Jason Gunthorpe
2017-11-05 11:05 ` Jarkko Sakkinen
2017-11-06 2:27 ` Jason Gunthorpe
2017-11-07 3:20 ` PrasannaKumar Muralidharan
2017-11-07 16:04 ` Jason Gunthorpe [this message]
2017-11-09 16:19 ` PrasannaKumar Muralidharan
2017-11-09 16:29 ` Jason Gunthorpe
2017-11-12 5:27 ` PrasannaKumar Muralidharan
2017-11-14 14:34 ` Jarkko Sakkinen
2017-11-17 13:28 ` Jarkko Sakkinen
2017-11-17 13:57 ` Jarkko Sakkinen
2018-01-27 6:50 ` PrasannaKumar Muralidharan
2018-01-29 22:06 ` Jarkko Sakkinen
2018-01-30 11:52 ` James Morris
2018-01-30 15:28 ` Jarkko Sakkinen
2017-11-07 19:24 ` 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=20171107160404.GG21466@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=linux-security-module@vger.kernel.org \
/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).