Linux kbuild/kconfig development
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: "Thomas Weißschuh" <linux@weissschuh.net>,
	"Nathan Chancellor" <nathan@kernel.org>,
	"Nicolas Schier" <nicolas@fjasle.eu>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Borislav Petkov" <bp@alien8.de>,
	"Dave Hansen" <dave.hansen@linux.intel.com>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	"Ben Hutchings" <ben@decadent.org.uk>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH 4/4] x86/boot/compressed: Switch to -ffile-prefix-map
Date: Sat, 15 Mar 2025 22:25:03 +0100	[thread overview]
Message-ID: <Z9XwL8v3-nIneMox@gmail.com> (raw)
In-Reply-To: <CAK7LNATuGr39YSsr0e6pB6wD7shyZVL12GMuE3HaWfXFXuRd4w@mail.gmail.com>


* Masahiro Yamada <masahiroy@kernel.org> wrote:

> Hi X86 maintainers,
> 
> Is it OK to pick up this to kbuild tree?
> Ack is appreciated.

Acked-by: Ingo Molnar <mingo@kernel.org>

Thank you for picking up these!

	Ingo

  reply	other threads:[~2025-03-15 21:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13 15:59 [PATCH 0/4] kbuild: make all file references relative to source root Thomas Weißschuh
2025-03-13 15:59 ` [PATCH 1/4] " Thomas Weißschuh
2025-03-13 15:59 ` [PATCH 2/4] kbuild: doc: reproducible-builds: drop section "Absolute filenames" Thomas Weißschuh
2025-03-13 15:59 ` [PATCH 3/4] x86/boot: Switch to -ffile-prefix-map Thomas Weißschuh
2025-03-15  8:15   ` Masahiro Yamada
2025-03-15 11:31     ` Borislav Petkov
2025-03-13 15:59 ` [PATCH 4/4] x86/boot/compressed: " Thomas Weißschuh
2025-03-15  8:16   ` Masahiro Yamada
2025-03-15 21:25     ` Ingo Molnar [this message]
2025-03-16  2:01       ` Masahiro Yamada
2025-03-15 11:34 ` [PATCH 0/4] kbuild: make all file references relative to source root Borislav Petkov
2025-03-15 12:02   ` Masahiro Yamada

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=Z9XwL8v3-nIneMox@gmail.com \
    --to=mingo@kernel.org \
    --cc=ben@decadent.org.uk \
    --cc=bp@alien8.de \
    --cc=corbet@lwn.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=masahiroy@kernel.org \
    --cc=mingo@redhat.com \
    --cc=nathan@kernel.org \
    --cc=nicolas@fjasle.eu \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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