From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751492AbdCRNPA (ORCPT ); Sat, 18 Mar 2017 09:15:00 -0400 Received: from conssluserg-03.nifty.com ([210.131.2.82]:62666 "EHLO conssluserg-03.nifty.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751337AbdCRNO6 (ORCPT ); Sat, 18 Mar 2017 09:14:58 -0400 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-03.nifty.com v2IDEg2S010956 X-Nifty-SrcIP: [209.85.161.173] MIME-Version: 1.0 In-Reply-To: References: <20161122213434.14788-1-mmarek@suse.com> <20170310175854.GE18894@arm.com> From: Masahiro Yamada Date: Sat, 18 Mar 2017 22:14:41 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 1/6] arm64: Use full path in KBUILD_IMAGE definition To: Michal Marek , Will Deacon Cc: Linux Kbuild mailing list , Linux Kernel Mailing List , Catalin Marinas , linux-arm-kernel Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Will, Michal, 2017-03-11 6:20 GMT+09:00 Michal Marek : > Dne 10.3.2017 v 18:58 Will Deacon napsal(a): >> 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 >>> Cc: Will Deacon >>> Cc: linux-arm-kernel@lists.infradead.org >>> Signed-off-by: Michal Marek >>> --- >>> arch/arm64/Makefile | 6 +++--- >>> 1 file changed, 3 insertions(+), 3 deletions(-) >> >> What's the plan for this patch? I'm happy to merge it, > > Great, please merge it. > > >> but I don't see >> the rest of the series queued anywhere. > > I'll see what remains and submit the rest via the kbuild tree. > > Thanks, > Michal > -- > To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html I like this approach, rather than fixing scripts/package/mkspec. So, how shall we handle this series? I am OK with getting 1/6 in through arm64 tree, but 6/6 will be postponed in the case. If Will issues Acked-by, I can pick-up the whole series to linux-kbuild. -- Best Regards Masahiro Yamada From mboxrd@z Thu Jan 1 00:00:00 1970 From: yamada.masahiro@socionext.com (Masahiro Yamada) Date: Sat, 18 Mar 2017 22:14:41 +0900 Subject: [PATCH 1/6] arm64: Use full path in KBUILD_IMAGE definition In-Reply-To: References: <20161122213434.14788-1-mmarek@suse.com> <20170310175854.GE18894@arm.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Will, Michal, 2017-03-11 6:20 GMT+09:00 Michal Marek : > Dne 10.3.2017 v 18:58 Will Deacon napsal(a): >> 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 >>> Cc: Will Deacon >>> Cc: linux-arm-kernel at lists.infradead.org >>> Signed-off-by: Michal Marek >>> --- >>> arch/arm64/Makefile | 6 +++--- >>> 1 file changed, 3 insertions(+), 3 deletions(-) >> >> What's the plan for this patch? I'm happy to merge it, > > Great, please merge it. > > >> but I don't see >> the rest of the series queued anywhere. > > I'll see what remains and submit the rest via the kbuild tree. > > Thanks, > Michal > -- > To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in > the body of a message to majordomo at vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html I like this approach, rather than fixing scripts/package/mkspec. So, how shall we handle this series? I am OK with getting 1/6 in through arm64 tree, but 6/6 will be postponed in the case. If Will issues Acked-by, I can pick-up the whole series to linux-kbuild. -- Best Regards Masahiro Yamada