linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Peter Huewe <peterhuewe@gmx.de>
Cc: zohar@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
	linux-integrity@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: update TPM driver infrastructure changes
Date: Fri, 3 Nov 2017 16:21:07 +0200	[thread overview]
Message-ID: <20171103142107.gdlooejtpehfkeez@linux.intel.com> (raw)
In-Reply-To: <5ac2c392-3ec2-4656-a185-6c9c554b8b2e@gmx.de>

On Tue, Oct 31, 2017 at 01:41:42AM +0100, Peter Huewe wrote:
> Hi,
> 
> Am Freitag, 29. September 2017 22:23:13 CEST schrieb Jarkko Sakkinen:
> > On Fri, Sep 29, 2017 at 08:29:09AM +0000, Peter.Huewe@infineon.com wrote:
> > > > ...
> > > Spinics is archiving us at
> > > https://www.spinics.net/lists/linux-integrity/
> > > 
> > > It would be good to add this to the vger page + documented on the
> > > wiki, which should be added to MAINTAINERS.
> > > http://kernsec.org/wiki/index.php/Linux_Kernel_Integrity as wiki page
> > > 
> > > 
> > > Peter ...
> > 
> > Can you submit a follow-up patch that adds this information?
> 
> I added the information to the kernsec wiki at
> http://kernsec.org/wiki/index.php/Linux_Kernel_Integrity
> 
> However, since your MAINTAINERS patch is neither upstream, nor in any of
> your
> branches (next / master) I cannot send an update.
> 
> About the wiki - I added quite a few other links, especially about tpm 2.0.
> If anyone wants to have any information added, please let me know.
> 
> I definitely would like to extend the wiki usage.
> So if you have any documents, e.g. - about how the patch flow is/should be,
> - how stuff gets tested
> - subsystem specific rules
> - subsystem architecuture
> 
> but also links to interesting pages/projects PLEASE let me know.
> 
> Thanks,
> Peter

Looks good to me.

/Jarkko

  reply	other threads:[~2017-11-03 14:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-15 22:38 [PATCH] MAINTAINERS: update TPM driver infrastructure changes Jarkko Sakkinen
2017-09-26 16:16 ` Mimi Zohar
2017-09-29  8:29   ` Peter.Huewe
2017-09-29 20:23     ` Jarkko Sakkinen
2017-10-31  0:41       ` Peter Huewe
2017-11-03 14:21         ` Jarkko Sakkinen [this message]
2017-09-29 16:59   ` Jarkko Sakkinen
2017-09-29 18:31     ` Aw: " Peter Huewe
2017-10-04  7:27       ` Jarkko Sakkinen
2017-10-04  7:33         ` Peter Huewe
2017-10-04 12:18           ` Jarkko Sakkinen
2017-10-19  8:10 ` Marc Zyngier

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=20171103142107.gdlooejtpehfkeez@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    --cc=zohar@linux.vnet.ibm.com \
    /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).