From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Eric Snowberg <eric.snowberg@oracle.com>
Cc: dhowells@redhat.com, dwmw2@infradead.org, masahiroy@kernel.org,
michal.lkml@markovi.net, keyrings@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 1/2] certs: Move load_system_certificate_list to a common function
Date: Wed, 30 Sep 2020 21:02:54 +0000 [thread overview]
Message-ID: <20200930210254.GB65339@linux.intel.com> (raw)
In-Reply-To: <20200930201508.35113-2-eric.snowberg@oracle.com>
On Wed, Sep 30, 2020 at 04:15:07PM -0400, Eric Snowberg wrote:
> Move functionality within load_system_certificate_list to a common
> function, so it can be reused in the future.
>
> Signed-off-by: Eric Snowberg <eric.snowberg@oracle.com>
I rather think now rather than the future. I think this should be part
of a patch set where the re-use actually happens.
Without that context, I rather not say anything about this patch.
Neither an issue for me if it gets applied. This is just a guideline
that I follow (in order to manage this chaos).
Looking at the code change, I do not see anything strikingly wrong in
it.
/Jarkko
WARNING: multiple messages have this Message-ID (diff)
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Eric Snowberg <eric.snowberg@oracle.com>
Cc: dhowells@redhat.com, dwmw2@infradead.org, masahiroy@kernel.org,
michal.lkml@markovi.net, keyrings@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 1/2] certs: Move load_system_certificate_list to a common function
Date: Thu, 1 Oct 2020 00:02:54 +0300 [thread overview]
Message-ID: <20200930210254.GB65339@linux.intel.com> (raw)
In-Reply-To: <20200930201508.35113-2-eric.snowberg@oracle.com>
On Wed, Sep 30, 2020 at 04:15:07PM -0400, Eric Snowberg wrote:
> Move functionality within load_system_certificate_list to a common
> function, so it can be reused in the future.
>
> Signed-off-by: Eric Snowberg <eric.snowberg@oracle.com>
I rather think now rather than the future. I think this should be part
of a patch set where the re-use actually happens.
Without that context, I rather not say anything about this patch.
Neither an issue for me if it gets applied. This is just a guideline
that I follow (in order to manage this chaos).
Looking at the code change, I do not see anything strikingly wrong in
it.
/Jarkko
next prev parent reply other threads:[~2020-09-30 21:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 20:15 [PATCH 0/2] Preloaded revocation keys Eric Snowberg
2020-09-30 20:15 ` Eric Snowberg
2020-09-30 20:15 ` [PATCH 1/2] certs: Move load_system_certificate_list to a common function Eric Snowberg
2020-09-30 20:15 ` Eric Snowberg
2020-09-30 21:02 ` Jarkko Sakkinen [this message]
2020-09-30 21:02 ` Jarkko Sakkinen
2020-09-30 21:15 ` Eric Snowberg
2020-09-30 21:15 ` Eric Snowberg
2020-09-30 21:49 ` Jarkko Sakkinen
2020-09-30 21:49 ` Jarkko Sakkinen
2020-09-30 20:15 ` [PATCH 2/2] certs: Add ability to preload revocation certs Eric Snowberg
2020-09-30 20:15 ` Eric Snowberg
2020-09-30 20:56 ` Jarkko Sakkinen
2020-09-30 20:56 ` Jarkko Sakkinen
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=20200930210254.GB65339@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=eric.snowberg@oracle.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
/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.