From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Yue Haibing" <yuehaibing@huawei.com>, <dhowells@redhat.com>
Cc: <keyrings@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] KEYS: Remove unused declarations
Date: Thu, 17 Aug 2023 00:06:09 +0300 [thread overview]
Message-ID: <CUU9WXZGDDO2.2E7XP03ITLLLY@suppilovahvero> (raw)
In-Reply-To: <20230816131122.43240-1-yuehaibing@huawei.com>
On Wed Aug 16, 2023 at 4:11 PM EEST, Yue Haibing wrote:
> These declarations are never implemented, remove it.
>
> Signed-off-by: Yue Haibing <yuehaibing@huawei.com>
> ---
> include/keys/dns_resolver-type.h | 4 ----
> include/linux/key.h | 3 ---
> 2 files changed, 7 deletions(-)
>
> diff --git a/include/keys/dns_resolver-type.h b/include/keys/dns_resolver-type.h
> index 218ca22fb056..1b89088a2837 100644
> --- a/include/keys/dns_resolver-type.h
> +++ b/include/keys/dns_resolver-type.h
> @@ -12,8 +12,4 @@
>
> extern struct key_type key_type_dns_resolver;
>
> -extern int request_dns_resolver_key(const char *description,
> - const char *callout_info,
> - char **data);
> -
> #endif /* _KEYS_DNS_RESOLVER_TYPE_H */
> diff --git a/include/linux/key.h b/include/linux/key.h
> index 938d7ecfb495..f16deadebca9 100644
> --- a/include/linux/key.h
> +++ b/include/linux/key.h
> @@ -436,9 +436,6 @@ extern key_ref_t keyring_search(key_ref_t keyring,
> const char *description,
> bool recurse);
>
> -extern int keyring_add_key(struct key *keyring,
> - struct key *key);
> -
> extern int keyring_restrict(key_ref_t keyring, const char *type,
> const char *restriction);
>
> --
> 2.34.1
Acked-by: Jarkko Sakkinen <jarkko@kernel.org>
David, can you pick this one?
BR, Jarkko
prev parent reply other threads:[~2023-08-16 21:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 13:11 [PATCH -next] KEYS: Remove unused declarations Yue Haibing
2023-08-16 21:06 ` 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=CUU9WXZGDDO2.2E7XP03ITLLLY@suppilovahvero \
--to=jarkko@kernel.org \
--cc=dhowells@redhat.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yuehaibing@huawei.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 read-only IMAP folder(s) and NNTP newsgroup(s).