From: <yamada.masahiro@socionext.com>
To: <kacper@kolodziej.it>, <michal.lkml@markovi.net>
Cc: <linux-kbuild@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] kbuild: [bin]deb-pkg: add DPKG_FLAGS variable
Date: Fri, 1 Mar 2019 07:14:41 +0000 [thread overview]
Message-ID: <87d286c0f28945728dd67b0ddf17375e@SOC-EX01V.e01.socionext.com> (raw)
In-Reply-To: <20190205123752.25432-1-kacper@kolodziej.it>
> -----Original Message-----
> From: Kacper Kołodziej [mailto:kacper@kolodziej.it]
> Sent: Tuesday, February 05, 2019 9:38 PM
> To: Yamada, Masahiro/山田 真弘 <yamada.masahiro@socionext.com>;
> michal.lkml@markovi.net
> Cc: linux-kbuild@vger.kernel.org; linux-kernel@vger.kernel.org;
> kacper@kolodziej.it
> Subject: [PATCH] kbuild: [bin]deb-pkg: add DPKG_FLAGS variable
>
> DPKG_FLAGS variable lets user to add more flags to dpkg-buildpackage
> command in deb-pkg and bindeb-pkg.
>
> Signed-off-by: Kacper Kołodziej <kacper@kolodziej.it>
> ---
Applied to linux-kbuild.
Thanks.
> scripts/package/Makefile | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/scripts/package/Makefile b/scripts/package/Makefile
> index 453fecee62f0..6963eacb323c 100644
> --- a/scripts/package/Makefile
> +++ b/scripts/package/Makefile
> @@ -72,11 +72,11 @@ deb-pkg: FORCE
> $(call cmd,src_tar,$(KDEB_SOURCENAME))
> origversion=$$(dpkg-parsechangelog -SVersion |sed
> 's/-[^-]*$$//');\
> mv
> $(KDEB_SOURCENAME).tar.gz ../$(KDEB_SOURCENAME)_$${origversion}.orig.t
> ar.gz
> - +dpkg-buildpackage -r$(KBUILD_PKG_ROOTCMD) -a$$(cat debian/arch)
> -i.git -us -uc
> + +dpkg-buildpackage -r$(KBUILD_PKG_ROOTCMD) -a$$(cat debian/arch)
> $(DPKG_FLAGS) -i.git -us -uc
>
> bindeb-pkg: FORCE
> $(CONFIG_SHELL) $(srctree)/scripts/package/mkdebian
> - +dpkg-buildpackage -r$(KBUILD_PKG_ROOTCMD) -a$$(cat debian/arch)
> -b -nc -uc
> + +dpkg-buildpackage -r$(KBUILD_PKG_ROOTCMD) -a$$(cat debian/arch)
> $(DPKG_FLAGS) -b -nc -uc
>
> intdeb-pkg: FORCE
> +$(CONFIG_SHELL) $(srctree)/scripts/package/builddeb
> --
> 2.20.1
prev parent reply other threads:[~2019-03-01 7:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 12:37 Kacper Kołodziej
2019-03-01 7:14 ` yamada.masahiro [this message]
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=87d286c0f28945728dd67b0ddf17375e@SOC-EX01V.e01.socionext.com \
--to=yamada.masahiro@socionext.com \
--cc=kacper@kolodziej.it \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.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
all inboxes | Powered by JetHome®