From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: tpmdd-devel@lists.sourceforge.net,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] tpm: move documentation under Documentation/security
Date: Mon, 7 Nov 2016 16:22:21 -0800 [thread overview]
Message-ID: <20161108002221.nclk5tmkbzexjtad@intel.com> (raw)
In-Reply-To: <20161107153752.3ddb0f52@lwn.net>
On Mon, Nov 07, 2016 at 03:37:52PM -0700, Jonathan Corbet wrote:
> On Thu, 3 Nov 2016 17:57:52 -0600
> Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> wrote:
>
> > In order too make Documentation root directory cleaner move the tpm
> > directory under Documentation/security.
>
> So I'll happily apply these to the docs tree, but...
>
> 1) It won't apply to current docs-next. I guess I can manage the merge
> there easily enough, but also,
>
> 2) Part 1 of the series (which wasn't sent to me anyway) is not something I
> an apply, so somebody else should pick that one up.
I'll apply the first patch to my (tpmdd) tree.
Thank you!
/Jarkko
prev parent reply other threads:[~2016-11-08 0:22 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
2016-11-07 22:37 ` Jonathan Corbet
2016-11-08 0:22 ` Jarkko Sakkinen [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=20161108002221.nclk5tmkbzexjtad@intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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
Powered by JetHome