From: jgg@ziepe.ca (Jason Gunthorpe)
To: linux-security-module@vger.kernel.org
Subject: [PATCH v2] tpm: Move Linux RNG connection to hwrng
Date: Sun, 5 Nov 2017 19:27:04 -0700 [thread overview]
Message-ID: <20171106022704.GD26011@ziepe.ca> (raw)
In-Reply-To: <20171105110506.usxmuzrvcjvxahr6@linux.intel.com>
On Sun, Nov 05, 2017 at 01:05:06PM +0200, Jarkko Sakkinen wrote:
> I asked to create a series for a reason. Now this doesn't apply because I
> don't have an ancestor in my git history.
It would be unusual for me to put your patch into a series unless I am
also adopting it. eg what happens if there are more comments on it?
Also, I wasn't sure what branch your patch was against since my tree
didn't have history for it either..
Sometimes the maintainer has to sort stuff like this out... :)
> Please resend as series together with my patch. I can apply neither yet
> because they have zero tested-by's.
Hopefully PrasannaKumar can test both patches.
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-06 2:27 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 [this message]
2017-11-07 3:20 ` PrasannaKumar Muralidharan
2017-11-07 16:04 ` Jason Gunthorpe
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=20171106022704.GD26011@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).