All of lore.kernel.org
 help / color / mirror / Atom feed
From: "longguang.yue" <bigclouds@163.com>
To: "Nicolas Schier" <nicolas.schier@linux.dev>
Cc: linux-kbuild@vger.kernel.org, nathan@kernel.org, masahiroy@kernel.org
Subject: Re:Re: [PATCH] Makefile: mrproper deletes signing_key.x509
Date: Mon, 11 Aug 2025 14:28:56 +0800 (CST)	[thread overview]
Message-ID: <1ac1d3e3.58ad.19897d159ff.Coremail.bigclouds@163.com> (raw)
In-Reply-To: <aJerjQGmXXcpTtBB@fjasle.eu>

Nicolas Schier, Hi:

  It should not delete x509.genkey because of its exsitence in gitignore.
Normally, users want to keep  a self-defined x509.genkey,  but mrproper deletes it, only default_x509.genkey is effective. 
After applying this patch, users just need to copy self-defined x509.genkey into certs directory once.

Thanks.


At 2025-08-10 04:11:57, "Nicolas Schier" <nicolas.schier@linux.dev> wrote:
>On Sat, Aug 09, 2025 at 08:04:05PM +0800 longguang.yue wrote:
>> deletes temporary signing_key.x509 and reserves user-defined x509.genkey
>
>can you elaborate the actual problem with some more details?
>
>certs/signing_key.x509 is removed during 'make clean' which is a dependency
>of 'mrproper'.
>
>'mrproper' is meant to remove everything that might influence a subsequent
>call of kbuild for the sane architecture.
>
>Without further details I cannot see any problem here.
>
>Kind regards,
>Nicolas

  reply	other threads:[~2025-08-11  6:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-09 12:04 [PATCH] Makefile: mrproper deletes signing_key.x509 longguang.yue
2025-08-09 20:11 ` Nicolas Schier
2025-08-11  6:28   ` longguang.yue [this message]
2025-08-11 13:59     ` Nicolas Schier
2025-08-11 19:14       ` Nathan Chancellor
2025-08-12  2:22         ` longguang.yue
2025-08-12  9:31       ` David Howells

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=1ac1d3e3.58ad.19897d159ff.Coremail.bigclouds@163.com \
    --to=bigclouds@163.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=nicolas.schier@linux.dev \
    /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.