public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Schier <nicolas@fjasle.eu>
To: Bastian Germann <bage@linutronix.de>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/1] kbuild: deb-pkg: default dpkg-buildpackage --build
Date: Mon, 6 Mar 2023 15:30:07 +0100	[thread overview]
Message-ID: <ZAX47xq+eQX41htE@buildd.core.avm.de> (raw)
In-Reply-To: <20230305232536.19528-1-bage@linutronix.de>

On Mon, Mar 06, 2023 at 12:25:34AM +0100, Bastian Germann wrote:
> deb-pkg's dpkg-buildpackage invocation was changed in v6.2, unnecessarily

v6.3

> adding the --build parameter explicitly. Revert the change.
> 
> Bastian Germann (1):
>   kbuild: deb-pkg: default dpkg-buildpackage --build
> 
>  scripts/Makefile.package | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> -- 
> 2.39.2
> 

Masahiro prepared a patch [1] for explicitly introducing a 'srcdeb-pkg'
target, but scheduled its inclusion for v6.4.

Kind regards,
Nicolas

[1]: https://lore.kernel.org/linux-kbuild/CAK7LNAR82ZgvKof9VMXRM4A_h22ZNCyoaKoHW-ONJ+4vctCu_A@mail.gmail.com/T/#m59cc003498dab9b7246198ac3172527256bd1304

  parent reply	other threads:[~2023-03-06 14:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-05 23:25 [PATCH 0/1] kbuild: deb-pkg: default dpkg-buildpackage --build Bastian Germann
2023-03-05 23:25 ` [PATCH 1/1] " Bastian Germann
2023-03-06 17:04   ` Nicolas Schier
2023-03-07  3:21   ` Masahiro Yamada
2023-03-07  8:44     ` Bastian Germann
2023-03-07 11:12       ` Masahiro Yamada
2023-03-07 11:20         ` [PATCH v2 0/1] " Bastian Germann
2023-03-07 11:20           ` [PATCH v2 1/1] " Bastian Germann
2023-03-10 14:37             ` Masahiro Yamada
2023-03-10 14:49               ` Bastian Germann
2023-03-10 15:25                 ` Bastian Germann
2023-03-06 14:30 ` Nicolas Schier [this message]
2023-03-06 14:36   ` [PATCH 0/1] " Bastian Germann

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=ZAX47xq+eQX41htE@buildd.core.avm.de \
    --to=nicolas@fjasle.eu \
    --cc=bage@linutronix.de \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox