All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.ibm.com>
To: Lakshmi Ramasubramanian <nramas@linux.microsoft.com>,
	James.Bottomley@HansenPartnership.com,
	linux-integrity@vger.kernel.org
Cc: dhowells@redhat.com, arnd@arndb.de, matthewgarrett@google.com,
	sashal@kernel.org, linux-kernel@vger.kernel.org,
	keyrings@vger.kernel.org
Subject: Re: [PATCH v8 0/3] IMA: Deferred measurement of keys
Date: Thu, 09 Jan 2020 05:07:22 +0000	[thread overview]
Message-ID: <1578546442.5147.37.camel@linux.ibm.com> (raw)
In-Reply-To: <20200109024359.3410-1-nramas@linux.microsoft.com>

On Wed, 2020-01-08 at 18:43 -0800, Lakshmi Ramasubramanian wrote:

> Changelog:
> 
>   v8
> 
>   => Rebased the changes to linux-next
>   => Need to apply the following patch first
>   https://lore.kernel.org/linux-integrity/20200108160508.5938-1-nramas@linux.microsoft.com/

Unless you made some other changes, the previous version of this patch
set is already in next-integrity-testing.  There's no reason to re-
post these patches again, and definitely not against linux-next.

Mimi

WARNING: multiple messages have this Message-ID (diff)
From: Mimi Zohar <zohar@linux.ibm.com>
To: Lakshmi Ramasubramanian <nramas@linux.microsoft.com>,
	James.Bottomley@HansenPartnership.com,
	linux-integrity@vger.kernel.org
Cc: dhowells@redhat.com, arnd@arndb.de, matthewgarrett@google.com,
	sashal@kernel.org, linux-kernel@vger.kernel.org,
	keyrings@vger.kernel.org
Subject: Re: [PATCH v8 0/3] IMA: Deferred measurement of keys
Date: Thu, 09 Jan 2020 00:07:22 -0500	[thread overview]
Message-ID: <1578546442.5147.37.camel@linux.ibm.com> (raw)
In-Reply-To: <20200109024359.3410-1-nramas@linux.microsoft.com>

On Wed, 2020-01-08 at 18:43 -0800, Lakshmi Ramasubramanian wrote:

> Changelog:
> 
>   v8
> 
>   => Rebased the changes to linux-next
>   => Need to apply the following patch first
>   https://lore.kernel.org/linux-integrity/20200108160508.5938-1-nramas@linux.microsoft.com/

Unless you made some other changes, the previous version of this patch
set is already in next-integrity-testing.  There's no reason to re-
post these patches again, and definitely not against linux-next.

Mimi


  parent reply	other threads:[~2020-01-09  5:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-09  2:42 [PATCH v8 0/3] IMA: Deferred measurement of keys Lakshmi Ramasubramanian
2020-01-09  2:42 ` Lakshmi Ramasubramanian
2020-01-09  2:42 ` [PATCH v8 1/3] IMA: Define workqueue for early boot key measurements Lakshmi Ramasubramanian
2020-01-09  2:42   ` Lakshmi Ramasubramanian
2020-01-09  2:42 ` [PATCH v8 2/3] IMA: Call workqueue functions to measure queued keys Lakshmi Ramasubramanian
2020-01-09  2:42   ` Lakshmi Ramasubramanian
2020-01-09  2:42 ` [PATCH v8 3/3] IMA: Defined timer to free " Lakshmi Ramasubramanian
2020-01-09  2:42   ` Lakshmi Ramasubramanian
2020-01-09  2:43 ` [PATCH v8 0/3] IMA: Deferred measurement of keys Lakshmi Ramasubramanian
2020-01-09  2:43   ` Lakshmi Ramasubramanian
2020-01-09  2:43   ` [PATCH v8 1/3] IMA: Define workqueue for early boot key measurements Lakshmi Ramasubramanian
2020-01-09  2:43     ` Lakshmi Ramasubramanian
2020-01-09  2:43   ` [PATCH v8 2/3] IMA: Call workqueue functions to measure queued keys Lakshmi Ramasubramanian
2020-01-09  2:43     ` Lakshmi Ramasubramanian
2020-01-09  2:43   ` [PATCH v8 3/3] IMA: Defined timer to free " Lakshmi Ramasubramanian
2020-01-09  2:43     ` Lakshmi Ramasubramanian
2020-01-09  5:07   ` Mimi Zohar [this message]
2020-01-09  5:07     ` [PATCH v8 0/3] IMA: Deferred measurement of keys Mimi Zohar
2020-01-09 16:47     ` Lakshmi Ramasubramanian
2020-01-09 16:47       ` Lakshmi Ramasubramanian

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=1578546442.5147.37.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=arnd@arndb.de \
    --cc=dhowells@redhat.com \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthewgarrett@google.com \
    --cc=nramas@linux.microsoft.com \
    --cc=sashal@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.