From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
linux-kernel@vger.kernel.org
Cc: linux-integrity@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: update TPM driver infrastructure changes
Date: Tue, 26 Sep 2017 12:16:20 -0400 [thread overview]
Message-ID: <1506442580.3677.97.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170915223811.21368-1-jarkko.sakkinen@linux.intel.com>
Hi Jarkko,
> +Q: https://patchwork.kernel.org/project/linux-integrity/list/
Is there a way of viewing not just the posted patches, but the
discussion as well? Do we need to set up an archive as well?
Mimi
WARNING: multiple messages have this Message-ID (diff)
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
linux-kernel@vger.kernel.org
Cc: linux-integrity@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: update TPM driver infrastructure changes
Date: Tue, 26 Sep 2017 12:16:20 -0400 [thread overview]
Message-ID: <1506442580.3677.97.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170915223811.21368-1-jarkko.sakkinen@linux.intel.com>
Hi Jarkko,
> +Q: https://patchwork.kernel.org/project/linux-integrity/list/
Is there a way of viewing not just the posted patches, but the
discussion as well? Do we need to set up an archive as well?
Mimi
next prev parent reply other threads:[~2017-09-26 16:16 UTC|newest]
Thread overview: 17+ 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 [this message]
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
2017-09-29 16:59 ` Jarkko Sakkinen
2017-09-29 16:59 ` Jarkko Sakkinen
2017-09-29 18:31 ` Aw: " Peter Huewe
2017-09-29 18:31 ` Peter Huewe
2017-10-04 7:27 ` Jarkko Sakkinen
2017-10-04 7:27 ` Jarkko Sakkinen
2017-10-04 7:33 ` Peter Huewe
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=1506442580.3677.97.camel@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.