mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <sha@pengutronix.de>
To: Bastian Krause <bst@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] crypto: skip make dependency for CONFIG_CRYPTO_RSA_KEY=__ENV__*
Date: Mon, 27 Jun 2022 08:56:53 +0200	[thread overview]
Message-ID: <20220627065653.GC19026@pengutronix.de> (raw)
In-Reply-To: <20220624141632.380159-1-bst@pengutronix.de>

On Fri, Jun 24, 2022 at 04:16:32PM +0200, Bastian Krause wrote:
> CONFIG_CRYPTO_RSA_KEY allows referring to environment variables, e.g.
> __ENV__FOO tells barebox' rsatoc to use the value of the environment
> variable "FOO".
> 
> There is no point in creating a make dependency for such values.
> Actually looking into the environment variable and deciding whether it is
> a PKCS#11 URI or a file seems unnecessarily complex. Let's filter out
> these special values and leave the error handling to rsatoc.
> 
> Fixes: a05ac5545c ("crypto: simplify $(srctree)/ handling and remove config_filename macro")
> Signed-off-by: Bastian Krause <bst@pengutronix.de>
> ---
>  crypto/Makefile | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Applied, thanks

Sascha

> 
> diff --git a/crypto/Makefile b/crypto/Makefile
> index 7e67f58bc7..762d7e543b 100644
> --- a/crypto/Makefile
> +++ b/crypto/Makefile
> @@ -28,7 +28,7 @@ $(obj)/rsa.o: $(obj)/rsa-keys.h
>  
>  CONFIG_CRYPTO_RSA_KEY := $(CONFIG_CRYPTO_RSA_KEY:"%"=%)
>  
> -ifneq ($(filter-out pkcs11:%, $(CONFIG_CRYPTO_RSA_KEY)),)
> +ifneq ($(filter-out pkcs11:% __ENV__%, $(CONFIG_CRYPTO_RSA_KEY)),)
>  RSA_DEP := $(CONFIG_CRYPTO_RSA_KEY)
>  endif
>  
> -- 
> 2.30.2
> 
> 
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



      reply	other threads:[~2022-06-27  6:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24 14:16 Bastian Krause
2022-06-27  6:56 ` Sascha Hauer [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=20220627065653.GC19026@pengutronix.de \
    --to=sha@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=bst@pengutronix.de \
    /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