From: Ryan Eatmon <reatmon@ti.com>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"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>,
<kernel@pengutronix.de>
Subject: Re: [PATCH] arm: gen-mach-types: don't include absolute filename
Date: Wed, 3 Jun 2026 13:58:58 -0500 [thread overview]
Message-ID: <8fe204a8-69e2-4739-8c40-ff72a1e5e889@ti.com> (raw)
In-Reply-To: <aiBDAQmQFKeN033y@monoceros>
On 6/3/2026 10:09 AM, Uwe Kleine-König wrote:
> 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>
Agreed.
Acked-by: Ryan Eatmon <reatmon@ti.com>
> Thanks
> Uwe
--
Ryan Eatmon reatmon@ti.com
-----------------------------------------
Texas Instruments, Inc. - LCPD - MGTS
next prev parent reply other threads:[~2026-06-03 18:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 14:12 Sascha Hauer
2026-06-03 15:09 ` Uwe Kleine-König
2026-06-03 18:58 ` Ryan Eatmon [this message]
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=8fe204a8-69e2-4739-8c40-ff72a1e5e889@ti.com \
--to=reatmon@ti.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=m.felsch@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--cc=u.kleine-koenig@baylibre.com \
/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®