From: jarkko.sakkinen@linux.intel.com (Jarkko Sakkinen)
To: linux-security-module@vger.kernel.org
Subject: Proposal: rename tpm1_eventlog.c and tpm2_eventlog.c
Date: Thu, 26 Oct 2017 16:14:29 +0200 [thread overview]
Message-ID: <20171026141429.nnmc2ks4m2bm6yhx@linux.intel.com> (raw)
In-Reply-To: <20171025131848.3il7j5rw7nt7e2l6@linux.intel.com>
On Wed, Oct 25, 2017 at 03:18:48PM +0200, Jarkko Sakkinen wrote:
> > Since this may conflict with the last patch set I sent, are you happy
> > for me to base this new set on tpmdd/master?
>
> What about this: you do an updated version of your patch set that
> includes these clean ups?
>
> PS. Sorry for slowness with your patches. I've just had a lot of stuff
> going on lately. They are 2nd in my priority queue right after
> CVE-2017-15361.
This is an awful idea as your patch is in great shape and we want to
land that feature ASAP. Lets land your patches first and then plan how
to do the clean up.
I have some other suggestions for the clean up work that require even
more work. Mainly: I think it would make sense to have an eventlog
subdirectory for the eventlog as it's growing so complex.
What do you think?
/Jarkko
--
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-10-26 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 22:21 Proposal: rename tpm1_eventlog.c and tpm2_eventlog.c Jarkko Sakkinen
2017-10-25 8:43 ` Thiebaud Weksteen
2017-10-25 13:18 ` Jarkko Sakkinen
2017-10-26 14:14 ` Jarkko Sakkinen [this message]
2017-10-27 9:13 ` Thiebaud Weksteen
2017-10-30 18:34 ` Nayna Jain
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=20171026141429.nnmc2ks4m2bm6yhx@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--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).