From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,kernel@pengutronix.de,u.kleine-koenig@pengutronix.de,akpm@linux-foundation.org
Subject: [to-be-updated] lib-build_oid_registry-dont-mention-the-full-path-of-the-script-in-output.patch removed from -mm tree
Date: Wed, 13 Mar 2024 07:49:59 -0700 [thread overview]
Message-ID: <20240313145000.AE6B9C433C7@smtp.kernel.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1854 bytes --]
The quilt patch titled
Subject: lib/build_OID_registry: Don't mention the full path of the script in output
has been removed from the -mm tree. Its filename was
lib-build_oid_registry-dont-mention-the-full-path-of-the-script-in-output.patch
This patch was dropped because an updated version will be merged
------------------------------------------------------
From: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Subject: lib/build_OID_registry: Don't mention the full path of the script in output
Date: Mon, 11 Mar 2024 12:01:22 +0100
This change strips the full path of the script generating
lib/oid_registry_data.c to just lib/build_OID_registry. The motivation
for this change is Yocto emitting a build warning
File /usr/src/debug/linux-lxatac/6.7-r0/lib/oid_registry_data.c in package linux-lxatac-src contains reference to TMPDIR [buildpaths]
So this change brings us one step closer to make the build result
reproducible independent of the build path.
Link: https://lkml.kernel.org/r/20240311110121.459581-2-u.kleine-koenig@pengutronix.de
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Cc: Pengutronix Kernel Team <kernel@pengutronix.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
lib/build_OID_registry | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/lib/build_OID_registry~lib-build_oid_registry-dont-mention-the-full-path-of-the-script-in-output
+++ a/lib/build_OID_registry
@@ -35,7 +35,7 @@ close IN_FILE || die;
#
open C_FILE, ">$ARGV[1]" or die;
print C_FILE "/*\n";
-print C_FILE " * Automatically generated by ", $0, ". Do not edit\n";
+print C_FILE " * Automatically generated by ", $0 =~ s#^\Q$ENV{'abs_srctree'}/\E##r, ". Do not edit\n";
print C_FILE " */\n";
#
_
Patches currently in -mm which might be from u.kleine-koenig@pengutronix.de are
reply other threads:[~2024-03-13 14:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240313145000.AE6B9C433C7@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=kernel@pengutronix.de \
--cc=mm-commits@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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.