linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mickaël Salaün" <mic@digikod.net>
To: David Howells <dhowells@redhat.com>
Cc: "David Woodhouse" <dwmw2@infradead.org>,
	"Jarkko Sakkinen" <jarkko@kernel.org>,
	"David S . Miller" <davem@davemloft.net>,
	"Herbert Xu" <herbert@gondor.apana.org.au>,
	"James Morris" <jmorris@namei.org>,
	"Mickaël Salaün" <mic@linux.microsoft.com>,
	"Mimi Zohar" <zohar@linux.ibm.com>,
	"Serge E . Hallyn" <serge@hallyn.com>,
	"Tyler Hicks" <tyhicks@linux.microsoft.com>,
	keyrings@vger.kernel.org, linux-crypto@vger.kernel.org,
	linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org
Subject: Re: [PATCH v5 0/5] Enable root to update the blacklist keyring
Date: Mon, 1 Feb 2021 17:51:11 +0100	[thread overview]
Message-ID: <702232df-e229-a716-b688-918fe7e168e8@digikod.net> (raw)
In-Reply-To: <9d95ec74-cc89-9e0c-dac8-c05ea52991ac@digikod.net>

It doesn't contain Jarkko's Tested-by and Reviewed-by tags though.

On 01/02/2021 17:48, Mickaël Salaün wrote:
> Hi,
> 
> Yes, you can pull this patchset from here:
> https://github.com/l0kod/linux branch dyn-auth-blacklist-v5 (commit
> 33b94bcd56843b4235c6ba4a44157b3c5a8792f1).
> 
>  Mickaël
> 
> 
> On 01/02/2021 14:07, David Howells wrote:
>>
>> Hi Mickaël,
>>
>> Do you have a public branch somewhere I can pull from?
>>
>> David
>>

  reply	other threads:[~2021-02-01 16:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210128191705.3568820-1-mic@digikod.net>
2021-01-30 20:41 ` [PATCH v5 0/5] Enable root to update the blacklist keyring Jarkko Sakkinen
2021-02-01 13:07 ` David Howells
2021-02-01 16:48   ` Mickaël Salaün
2021-02-01 16:51     ` Mickaël Salaün [this message]
2021-02-01 17:08     ` David Howells

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=702232df-e229-a716-b688-918fe7e168e8@digikod.net \
    --to=mic@digikod.net \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=jarkko@kernel.org \
    --cc=jmorris@namei.org \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mic@linux.microsoft.com \
    --cc=serge@hallyn.com \
    --cc=tyhicks@linux.microsoft.com \
    --cc=zohar@linux.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).