All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Jun ASAKA <JunASAKA@zzy040330.moe>
Cc: masahiroy@kernel.org, ndesaulniers@google.com, nicolas@fjasle.eu,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: add a missing line for help message
Date: Tue, 27 Dec 2022 09:54:30 -0700	[thread overview]
Message-ID: <Y6sjRvdmzGqer5oL@dev-arch.thelio-3990X> (raw)
In-Reply-To: <20221227092157.329109-1-JunASAKA@zzy040330.moe>

On Tue, Dec 27, 2022 at 05:21:57PM +0800, Jun ASAKA wrote:
> The help message line for building the source RPM package was missing.
> Added it.
> 
> Signed-off-by: Jun ASAKA <JunASAKA@zzy040330.moe>

Thank you for the patch!

Reviewed-by: Nathan Chancellor <nathan@kernel.org>

> ---
>  scripts/Makefile.package | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/scripts/Makefile.package b/scripts/Makefile.package
> index 539e9f765d64..525a2820976f 100644
> --- a/scripts/Makefile.package
> +++ b/scripts/Makefile.package
> @@ -158,6 +158,7 @@ $(perf-tar-pkgs):
>  PHONY += help
>  help:
>  	@echo '  rpm-pkg             - Build both source and binary RPM kernel packages'
> +	@echo '  srcrpm-pkg          - Build only the source kernel RPM package'
>  	@echo '  binrpm-pkg          - Build only the binary kernel RPM package'
>  	@echo '  deb-pkg             - Build both source and binary deb kernel packages'
>  	@echo '  bindeb-pkg          - Build only the binary kernel deb package'
> -- 
> 2.31.1
> 

  reply	other threads:[~2022-12-27 16:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-27  9:21 [PATCH] kbuild: add a missing line for help message Jun ASAKA
2022-12-27 16:54 ` Nathan Chancellor [this message]
2022-12-29  2:15 ` 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=Y6sjRvdmzGqer5oL@dev-arch.thelio-3990X \
    --to=nathan@kernel.org \
    --cc=JunASAKA@zzy040330.moe \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=nicolas@fjasle.eu \
    /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.