From: Jarkko Sakkinen <jarkko@kernel.org>
To: David Howells <dhowells@redhat.com>
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
James Morris <jmorris@namei.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Jarkko Sakkinen <jarkko.sakkinen@iki.fi>,
Jann Horn <jannh@google.com>,
Gabriel Krisman Bertazi <krisman@collabora.com>,
"Alexander A. Klimov" <grandmaster@al2klimov.de>,
Ben Boeckel <mathstuf@gmail.com>,
linux-security-module@vger.kernel.org,
Denis Efremov <efremov@linux.com>,
keyrings@vger.kernel.org,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>, Tom Rix <trix@redhat.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/9] keys: Miscellaneous fixes
Date: Wed, 2 Dec 2020 18:43:25 +0200 [thread overview]
Message-ID: <20201202164325.GA89981@kernel.org> (raw)
In-Reply-To: <3093311.1606728092@warthog.procyon.org.uk>
On Mon, Nov 30, 2020 at 09:21:32AM +0000, David Howells wrote:
> Jarkko Sakkinen <jarkko@kernel.org> wrote:
>
> > I think that looks good, thank you. I'm sending PR next week. Should I
> > bundle those to that?
>
> I've updated the branch to include an ack from you, plus added the
> semicolon-removal patch and a #include-removal patch.
>
> You can try sending them on, though I don't think any of them are really
> critical patches (and we are in -rc6).
>
> David
I think I'll pass then and focus on SGX for the time being. Getting that
to the mainline will release quite a lot of bandwidth, i.e. on average
the best way to go forward.
I'll test this patch set once we are in 5.11-rc1:
https://lore.kernel.org/keyrings/20201120180426.922572-1-mic@digikod.net/
/Jarkko
prev parent reply other threads:[~2020-12-02 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 16:45 [PATCH 0/9] keys: Miscellaneous fixes David Howells
2020-11-27 16:46 ` [PATCH 6/9] security: keys: delete repeated words in comments David Howells
2020-11-29 3:38 ` [PATCH 0/9] keys: Miscellaneous fixes Jarkko Sakkinen
2020-11-30 9:21 ` David Howells
2020-12-02 16:43 ` 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=20201202164325.GA89981@kernel.org \
--to=jarkko@kernel.org \
--cc=dhowells@redhat.com \
--cc=efremov@linux.com \
--cc=grandmaster@al2klimov.de \
--cc=gustavoars@kernel.org \
--cc=jannh@google.com \
--cc=jarkko.sakkinen@iki.fi \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=krisman@collabora.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mathstuf@gmail.com \
--cc=rdunlap@infradead.org \
--cc=serge@hallyn.com \
--cc=trix@redhat.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).