mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Masahiro Yamada <masahiroy@kernel.org>, linux-kbuild@vger.kernel.org
Cc: Ard Biesheuvel <ardb@kernel.org>,
	Ben Hutchings <ben@decadent.org.uk>,
	Jonathan Corbet <corbet@lwn.net>,
	Nathan Chancellor <nathan@kernel.org>,
	Nicolas Schier <nicolas.schier@linux.dev>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: kbuild: note CONFIG_DEBUG_EFI in reproducible builds
Date: Wed, 25 Jun 2025 10:07:21 -0700	[thread overview]
Message-ID: <0f006fbf-c930-40aa-b08a-8e1b7275ea43@infradead.org> (raw)
In-Reply-To: <20250625125809.2504963-1-masahiroy@kernel.org>

Hi,

On 6/25/25 5:57 AM, Masahiro Yamada wrote:
> CONFIG_EFI_DEBUG embeds absolute file paths into object files, which
> makes the resulting vmlinux specific to the build environment.
> 
> Add a note about this in reproducible-builds.rst
> 
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> ---
> 
>  Documentation/kbuild/reproducible-builds.rst | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/Documentation/kbuild/reproducible-builds.rst b/Documentation/kbuild/reproducible-builds.rst
> index f2dcc39044e6..7a16dbc275ca 100644
> --- a/Documentation/kbuild/reproducible-builds.rst
> +++ b/Documentation/kbuild/reproducible-builds.rst
> @@ -61,6 +61,9 @@ supported.
>  The Reproducible Builds web site has more information about these
>  `prefix-map options`_.
>  
> +Some CONFIG options such as `CONFIG_DEBUG_EFI` embeds absolute paths in

               options                            embed

> +object files. Such options should be disabled.
> +
>  Generated files in source packages
>  ----------------------------------
>  

-- 
~Randy


      reply	other threads:[~2025-06-25 17:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-25 12:57 Masahiro Yamada
2025-06-25 17:07 ` Randy Dunlap [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=0f006fbf-c930-40aa-b08a-8e1b7275ea43@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=ardb@kernel.org \
    --cc=ben@decadent.org.uk \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®