All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Michal Marek <mmarek@suse.com>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	Catalin Marinas <catalin.marinas@arm.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/6] arm64: Use full path in KBUILD_IMAGE definition
Date: Fri, 10 Mar 2017 17:58:55 +0000	[thread overview]
Message-ID: <20170310175854.GE18894@arm.com> (raw)
In-Reply-To: <20161122213434.14788-1-mmarek@suse.com>

Hi Michael,

On Tue, Nov 22, 2016 at 10:34:29PM +0100, Michal Marek wrote:
> The KBUILD_IMAGE variable is used by the rpm and deb-pkg targets, which
> expect it to point to the image file in the build directory. The
> builddeb script has a workaround for architectures which only provide
> the basename, but let's provide a clean interface for packaging tools.
> 
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: linux-arm-kernel@lists.infradead.org
> Signed-off-by: Michal Marek <mmarek@suse.com>
> ---
>  arch/arm64/Makefile | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)

What's the plan for this patch? I'm happy to merge it, but I don't see
the rest of the series queued anywhere.

Thanks,

Will

> diff --git a/arch/arm64/Makefile b/arch/arm64/Makefile
> index 3635b8662724..80b6866bcacb 100644
> --- a/arch/arm64/Makefile
> +++ b/arch/arm64/Makefile
> @@ -94,12 +94,12 @@ libs-y		:= arch/arm64/lib/ $(libs-y)
>  core-$(CONFIG_EFI_STUB) += $(objtree)/drivers/firmware/efi/libstub/lib.a
>  
>  # Default target when executing plain make
> -KBUILD_IMAGE	:= Image.gz
> +boot		:= arch/arm64/boot
> +KBUILD_IMAGE	:= $(boot)/Image.gz
>  KBUILD_DTBS	:= dtbs
>  
> -all:	$(KBUILD_IMAGE) $(KBUILD_DTBS)
> +all:	Image.gz $(KBUILD_DTBS)
>  
> -boot := arch/arm64/boot
>  
>  Image: vmlinux
>  	$(Q)$(MAKE) $(build)=$(boot) $(boot)/$@
> -- 
> 2.10.0
> 

WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/6] arm64: Use full path in KBUILD_IMAGE definition
Date: Fri, 10 Mar 2017 17:58:55 +0000	[thread overview]
Message-ID: <20170310175854.GE18894@arm.com> (raw)
In-Reply-To: <20161122213434.14788-1-mmarek@suse.com>

Hi Michael,

On Tue, Nov 22, 2016 at 10:34:29PM +0100, Michal Marek wrote:
> The KBUILD_IMAGE variable is used by the rpm and deb-pkg targets, which
> expect it to point to the image file in the build directory. The
> builddeb script has a workaround for architectures which only provide
> the basename, but let's provide a clean interface for packaging tools.
> 
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: linux-arm-kernel at lists.infradead.org
> Signed-off-by: Michal Marek <mmarek@suse.com>
> ---
>  arch/arm64/Makefile | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)

What's the plan for this patch? I'm happy to merge it, but I don't see
the rest of the series queued anywhere.

Thanks,

Will

> diff --git a/arch/arm64/Makefile b/arch/arm64/Makefile
> index 3635b8662724..80b6866bcacb 100644
> --- a/arch/arm64/Makefile
> +++ b/arch/arm64/Makefile
> @@ -94,12 +94,12 @@ libs-y		:= arch/arm64/lib/ $(libs-y)
>  core-$(CONFIG_EFI_STUB) += $(objtree)/drivers/firmware/efi/libstub/lib.a
>  
>  # Default target when executing plain make
> -KBUILD_IMAGE	:= Image.gz
> +boot		:= arch/arm64/boot
> +KBUILD_IMAGE	:= $(boot)/Image.gz
>  KBUILD_DTBS	:= dtbs
>  
> -all:	$(KBUILD_IMAGE) $(KBUILD_DTBS)
> +all:	Image.gz $(KBUILD_DTBS)
>  
> -boot := arch/arm64/boot
>  
>  Image: vmlinux
>  	$(Q)$(MAKE) $(build)=$(boot) $(boot)/$@
> -- 
> 2.10.0
> 

  parent reply	other threads:[~2017-03-10 17:58 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-22 21:34 [PATCH 1/6] arm64: Use full path in KBUILD_IMAGE definition Michal Marek
2016-11-22 21:34 ` Michal Marek
2016-11-22 21:34 ` [PATCH 2/6] arm: " Michal Marek
2016-11-22 21:34   ` Michal Marek
2017-03-20 13:53   ` Masahiro Yamada
2017-03-20 13:53     ` Masahiro Yamada
2016-11-22 21:34 ` [PATCH 3/6] arc: " Michal Marek
2016-11-22 21:34   ` Michal Marek
2016-11-23 19:40   ` Alexey Brodkin
2016-11-23 19:40     ` Alexey Brodkin
2016-11-25 14:21     ` Michal Marek
2016-11-25 14:21       ` Michal Marek
2017-03-20 13:54   ` Masahiro Yamada
2017-03-20 13:54     ` Masahiro Yamada
2016-11-22 21:34 ` [PATCH 4/6] sh: " Michal Marek
2016-11-22 21:34   ` Michal Marek
2017-03-20 13:54   ` Masahiro Yamada
2017-03-20 13:54     ` Masahiro Yamada
2016-11-22 21:34 ` [PATCH 5/6] unicore32: " Michal Marek
2017-03-20 13:55   ` Masahiro Yamada
2016-11-22 21:34 ` [PATCH 6/6] deb-pkg: Remove the KBUILD_IMAGE workaround Michal Marek
2016-11-25 12:12   ` Riku Voipio
2016-11-25 14:22     ` Michal Marek
2017-03-20 13:56       ` Masahiro Yamada
2017-03-10 17:58 ` Will Deacon [this message]
2017-03-10 17:58   ` [PATCH 1/6] arm64: Use full path in KBUILD_IMAGE definition Will Deacon
2017-03-10 21:20   ` Michal Marek
2017-03-10 21:20     ` Michal Marek
2017-03-18 13:14     ` Masahiro Yamada
2017-03-18 13:14       ` Masahiro Yamada
2017-03-20 12:13       ` Will Deacon
2017-03-20 12:13         ` Will Deacon
2017-03-20 13:52         ` Masahiro Yamada
2017-03-20 13:52           ` Masahiro Yamada

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=20170310175854.GE18894@arm.com \
    --to=will.deacon@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.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 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.