Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Frias <sf84@laposte.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux: use $(LINUX_INSTALL_IMAGE_CMDS) instead of plain 'cp'
Date: Mon, 25 Apr 2016 14:17:50 +0200	[thread overview]
Message-ID: <571E0AEE.3010002@laposte.net> (raw)
In-Reply-To: <20160425140615.11e86412@free-electrons.com>

Hi Thomas,

On 04/25/2016 02:06 PM, Thomas Petazzoni wrote:
> Hello,
> 
> Thanks for reporting the problem, and thanks for your patch!

Sure! That's what Open Source is for! :-)

> 
>> diff --git a/linux/linux.mk b/linux/linux.mk
>> index 317587f..1f93074 100644
>> --- a/linux/linux.mk
>> +++ b/linux/linux.mk
>> @@ -330,7 +330,7 @@ ifeq ($(BR2_LINUX_KERNEL_APPENDED_DTB),y)
>>  # appended DTBs.
>>  define LINUX_INSTALL_IMAGE
>>  	mkdir -p $(1)
>> -	cp $(KERNEL_ARCH_PATH)/boot/$(LINUX_IMAGE_NAME).* $(1)
>> +	cp -v $(KERNEL_ARCH_PATH)/boot/$(LINUX_IMAGE_NAME).* $(1)
> 
> I think you did this change for debugging (which is OK), but it should
> be kept in your patch.

Ok, I will remove it.

> 
>>  endef
>>  else
>>  # Otherwise, just install the unique image generated by the kernel
>> @@ -447,8 +447,8 @@ $(LINUX_DIR)/.stamp_initramfs_rebuilt:
>> $(LINUX_DIR)/.stamp_target_installed $(LI
>>  	# Build the kernel.
>>  	$(LINUX_MAKE_ENV) $(MAKE) $(LINUX_MAKE_FLAGS) -C $(@D)
>> $(LINUX_TARGET_NAME)

This line is also present on LINUX_BUILD_CMDS, any reason not to reuse it?
LINUX_BUILD_CMDS does a couple of more things than what is done here,
like like running LINUX_BUILD_DTB or 'make modules', and maybe that is
not wanted?

>>  	$(LINUX_APPEND_DTB)
>> -	# Copy the kernel image to its final destination
>> -	cp $(LINUX_IMAGE_PATH) $(BINARIES_DIR)
>> +	# Copy the kernel image(s) to its(their) final destination
>> +	$(LINUX_INSTALL_IMAGES_CMDS)
> 
> I think I would prefer to have:
> 
> 	$(call LINUX_INSTALL_IMAGE,$(BINARIES_DIR))
> 

Ok, just wondering, why? I mean, IIUC, LINUX_INSTALL_IMAGES_CMDS also
handles the DTB copy when APPENDED_DTB is not set, right?

Best regards,

Sebastian

  parent reply	other threads:[~2016-04-25 12:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-25 11:58 [Buildroot] [PATCH] linux: use $(LINUX_INSTALL_IMAGE_CMDS) instead of plain 'cp' Sebastian Frias
2016-04-25 12:06 ` Thomas Petazzoni
2016-04-25 12:13   ` Thomas Petazzoni
2016-04-25 12:17   ` Sebastian Frias [this message]
2016-04-25 12:23     ` Thomas Petazzoni
2016-04-25 12:44       ` Sebastian Frias
2016-04-25 14:52   ` [Buildroot] [PATCH v2] " Sebastian Frias
2016-04-25 19:43     ` Thomas Petazzoni
2016-04-26  8:44       ` Sebastian Frias

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=571E0AEE.3010002@laposte.net \
    --to=sf84@laposte.net \
    --cc=buildroot@busybox.net \
    /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