From: "Uwe Kleine-König" <u.kleine-koenig@baylibre•com>
To: Sascha Hauer <s.hauer@pengutronix•de>
Cc: Russell King <linux@armlinux•org.uk>,
linux-arm-kernel@lists•infradead.org,
linux-kernel@vger•kernel.org,
Marco Felsch <m.felsch@pengutronix•de>,
Alexander Stein <alexander.stein@ew•tq-group.com>,
Ryan Eatmon <reatmon@ti•com>,
kernel@pengutronix•de
Subject: Re: [PATCH] arm: gen-mach-types: don't include absolute filename
Date: Wed, 3 Jun 2026 17:09:42 +0200 [thread overview]
Message-ID: <aiBDAQmQFKeN033y@monoceros> (raw)
In-Reply-To: <20260603-arm-remove-path-from-mach-types-h-v1-1-cda9890ba788@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 672 bytes --]
Hello Sascha,
On Wed, Jun 03, 2026 at 04:12:10PM +0200, Sascha Hauer wrote:
> mach-types.h is part of the kapi and as such shipped in the
> linux-headers package. The embedded build path makes that package
> non-reproducible without going through an extra step of normalizing the
> path. YOCTO has similar problems in the kernel debug source package.
>
> Make the path relative to the kernel source tree which is enough to
> find the tool that has generated the file.
>
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix•de>
Compared to my old patch this is simpler, I like it.
Acked-by: Uwe Kleine-König <u.kleine-koenig@baylibre•com>
Thanks
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-06-03 15:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 14:12 [PATCH] arm: gen-mach-types: don't include absolute filename Sascha Hauer
2026-06-03 15:09 ` Uwe Kleine-König [this message]
2026-06-03 18:58 ` Ryan Eatmon
2026-06-04 5:26 ` Alexander Stein
-- strict thread matches above, loose matches on Subject: below --
2024-11-14 13:00 Marco Felsch
2025-09-19 9:46 ` Lucas Stach
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=aiBDAQmQFKeN033y@monoceros \
--to=u.kleine-koenig@baylibre$(echo .)com \
--cc=alexander.stein@ew$(echo .)tq-group.com \
--cc=kernel@pengutronix$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux@armlinux$(echo .)org.uk \
--cc=m.felsch@pengutronix$(echo .)de \
--cc=reatmon@ti$(echo .)com \
--cc=s.hauer@pengutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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