From: James Morris <jmorris@namei.org>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
tpmdd-devel@lists.sourceforge.net,
Jonathan Corbet <corbet@lwn.net>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH 3/3] tpm: move documentation under Documentation/security
Date: Sat, 5 Nov 2016 03:34:40 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.20.1611050334130.16440@namei.org> (raw)
In-Reply-To: <20161104130102.pm4ggspfbyemrx6u@intel.com>
On Fri, 4 Nov 2016, Jarkko Sakkinen wrote:
> On Fri, Nov 04, 2016 at 02:06:00PM +0200, Jani Nikula wrote:
> > On Fri, 04 Nov 2016, Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> wrote:
> > > In order too make Documentation root directory cleaner move the tpm
> > > directory under Documentation/security.
> >
> > FWIW I like this.
>
> Thx. I just realized that I should have CC'd to linux-security-module
> to get say from James as this makes path for the whole security tree.
>
> James, sorry about that. Can you share your opinion?
Looks like a good idea to me.
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2016-11-04 16:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161103235752.19256-1-jarkko.sakkinen@linux.intel.com>
2016-11-03 23:57 ` [PATCH 1/3] tpm, tpm_vtpm_proxy: add kdoc comments for VTPM_PROXY_IOC_NEW_DEV Jarkko Sakkinen
2016-11-05 3:00 ` Jarkko Sakkinen
2016-11-07 0:46 ` Stefan Berger
2016-11-03 23:57 ` [PATCH 2/3] tpm: transition tpm_vtpm_proxy documentation to the Sphinx Jarkko Sakkinen
2016-11-05 3:01 ` Jarkko Sakkinen
2016-11-07 0:47 ` Stefan Berger
2016-11-03 23:57 ` [PATCH 3/3] tpm: move documentation under Documentation/security Jarkko Sakkinen
2016-11-04 12:06 ` Jani Nikula
2016-11-04 13:01 ` Jarkko Sakkinen
2016-11-04 16:34 ` James Morris [this message]
2016-11-07 22:37 ` Jonathan Corbet
2016-11-08 0:22 ` 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=alpine.LRH.2.20.1611050334130.16440@namei.org \
--to=jmorris@namei.org \
--cc=corbet@lwn.net \
--cc=jani.nikula@linux.intel.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=tpmdd-devel@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®