From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: David Howells <dhowells@redhat.com>, David Miller <davem@davemloft.net>
Cc: longman@redhat.com, jmorris@namei.org, serge@hallyn.com,
zohar@linux.ibm.com, kuba@kernel.org, keyrings@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-integrity@vger.kernel.org, netdev@vger.kernel.org,
linux-afs@lists.infradead.org, sumit.garg@linaro.org,
jsnitsel@redhat.com, roberto.sassu@huawei.com,
ebiggers@google.com, crecklin@redhat.com
Subject: Re: [PATCH v8 0/2] KEYS: Read keys to internal buffer & then copy to userspace
Date: Fri, 27 Mar 2020 00:37:30 +0200 [thread overview]
Message-ID: <c3a91d6d572d4975a8a5d3dbf004e46d7f59be78.camel@linux.intel.com> (raw)
In-Reply-To: <996368.1585246352@warthog.procyon.org.uk>
On Thu, 2020-03-26 at 18:12 +0000, David Howells wrote:
> David Miller <davem@davemloft.net> wrote:
>
> > Who will integrate these changes?
>
> I'll do it unless Jarkko wants to push it through his tree.
Please do.
/Jarkko
prev parent reply other threads:[~2020-03-26 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-22 1:11 [PATCH v8 0/2] KEYS: Read keys to internal buffer & then copy to userspace Waiman Long
2020-03-22 1:11 ` [PATCH v8 1/2] KEYS: Don't write out to userspace while holding key semaphore Waiman Long
2020-03-22 1:11 ` [PATCH v8 2/2] KEYS: Avoid false positive ENOMEM error on key read Waiman Long
2020-03-26 2:30 ` [PATCH v8 0/2] KEYS: Read keys to internal buffer & then copy to userspace David Miller
2020-03-26 18:12 ` David Howells
2020-03-26 22:37 ` 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=c3a91d6d572d4975a8a5d3dbf004e46d7f59be78.camel@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=crecklin@redhat.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=ebiggers@google.com \
--cc=jmorris@namei.org \
--cc=jsnitsel@redhat.com \
--cc=keyrings@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=longman@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=roberto.sassu@huawei.com \
--cc=serge@hallyn.com \
--cc=sumit.garg@linaro.org \
--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).