All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Kairui Song <kasong@redhat.com>
Cc: dhowells@redhat.com, linux-kernel@vger.kernel.org,
	dwmw2@infradead.org, jwboyer@fedoraproject.org,
	keyrings@vger.kernel.org, jmorris@namei.org, serge@hallyn.com,
	zohar@linux.ibm.com, bauerman@linux.ibm.com, ebiggers@google.com,
	nayna@linux.ibm.com, dyoung@redhat.com
Subject: Re: [RFC PATCH 1/1] KEYS, integrity: Link .platform keyring to .secondary_trusted_keys
Date: Thu, 17 Jan 2019 15:04:21 +0000	[thread overview]
Message-ID: <21896.1547737461@warthog.procyon.org.uk> (raw)
In-Reply-To: <20190108081247.2266-2-kasong@redhat.com>

Kairui Song <kasong@redhat.com> wrote:

> +extern const struct key* __init integrity_get_platform_keyring(void);

This should really be in keys/system_keyring.h and probably shouldn't be
exposed directly if it can be avoided.

David

  parent reply	other threads:[~2019-01-17 15:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-08  8:12 [RFC PATCH 0/1] KEYS, integrity: Link .platform keyring to .secondary_trusted_keys Kairui Song
2019-01-08  8:12 ` Kairui Song
2019-01-08  8:12 ` [RFC PATCH 1/1] " Kairui Song
2019-01-08  8:12   ` Kairui Song
2019-01-08 15:18   ` Mimi Zohar
2019-01-08 15:18     ` Mimi Zohar
2019-01-09  1:33     ` Dave Young
2019-01-09  1:33       ` Dave Young
2019-01-09  1:33       ` Dave Young
2019-01-09  2:02       ` Kairui Song
2019-01-09  2:02         ` Kairui Song
2019-01-09  2:02         ` Kairui Song
2019-01-09 14:07       ` Mimi Zohar
2019-01-09 14:07         ` Mimi Zohar
2019-01-09 14:07         ` Mimi Zohar
2019-01-08 14:31 ` [RFC PATCH 0/1] " Mimi Zohar
2019-01-08 14:31   ` Mimi Zohar
2019-01-17 15:04 ` David Howells [this message]
2019-01-17 16:15   ` [RFC PATCH 1/1] " Kairui Song
2019-01-17 16:15     ` Kairui Song

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=21896.1547737461@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=bauerman@linux.ibm.com \
    --cc=dwmw2@infradead.org \
    --cc=dyoung@redhat.com \
    --cc=ebiggers@google.com \
    --cc=jmorris@namei.org \
    --cc=jwboyer@fedoraproject.org \
    --cc=kasong@redhat.com \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nayna@linux.ibm.com \
    --cc=serge@hallyn.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 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.