All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@fb.com>
To: <linux-kbuild@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Keith Busch <kbusch@kernel.org>, Masahiro Yamada <masahiroy@kernel.org>
Subject: [PATCH] kbuild: show the install image name and path
Date: Wed, 1 Jun 2022 18:50:50 -0700	[thread overview]
Message-ID: <20220602015050.3185028-1-kbusch@fb.com> (raw)

From: Keith Busch <kbusch@kernel.org>

Prior to commit f774f5bb87d13 ("kbuild: factor out the common
installation code into"), a 'make install' would print out the install
command like:

  sh ./arch/x86/boot/install.sh 5.18.0-11935-gbffe08031c89 \
        arch/x86/boot/bzImage System.map "/boot"

This output was very useful for my workflow, so this patch prints it out
again. I'm not sure if there's a better way to do this than what's
implemented here, so any feedback is appreciated.

Cc: Masahiro Yamada <masahiroy@kernel.org>
Signed-off-by: Keith Busch <kbusch@kernel.org>
---
 scripts/install.sh | 1 +
 1 file changed, 1 insertion(+)

diff --git a/scripts/install.sh b/scripts/install.sh
index 9bb0fb44f04a..2989d25ef069 100755
--- a/scripts/install.sh
+++ b/scripts/install.sh
@@ -33,6 +33,7 @@ do
 	# installkernel(8) says the parameters are like follows:
 	#
 	#   installkernel version zImage System.map [directory]
+	echo "$0 ${KERNELRELEASE} ${KBUILD_IMAGE} ${INSTALL_PATH}"
 	exec "${file}" "${KERNELRELEASE}" "${KBUILD_IMAGE}" System.map "${INSTALL_PATH}"
 done
 
-- 
2.30.2


             reply	other threads:[~2022-06-02  1:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02  1:50 Keith Busch [this message]
2022-06-02 14:52 ` [PATCH] kbuild: show the install image name and path Masahiro Yamada
2022-06-02 15:04   ` Randy Dunlap
2022-06-02 16:26   ` Keith Busch

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=20220602015050.3185028-1-kbusch@fb.com \
    --to=kbusch@fb.com \
    --cc=kbusch@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@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 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.