mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	Ben Hutchings <ben@decadent.org.uk>,
	Nicolas Schier <nicolas@fjasle.eu>
Subject: Re: [PATCH] kbuild: deb-pkg: remove "version" variable in mkdebian
Date: Tue, 11 Mar 2025 20:19:00 +0100	[thread overview]
Message-ID: <20250311191900.GB1958594@ax162> (raw)
In-Reply-To: <20250311190238.634226-1-masahiroy@kernel.org>

On Wed, Mar 12, 2025 at 04:02:24AM +0900, Masahiro Yamada wrote:
> ${version} and ${KERNELRELEASE} are the same.
> 
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>

Always love less indirection.

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

> ---
> 
>  scripts/package/mkdebian | 17 ++++++++---------
>  1 file changed, 8 insertions(+), 9 deletions(-)
> 
> diff --git a/scripts/package/mkdebian b/scripts/package/mkdebian
> index 80ed96561993..6685d13737c1 100755
> --- a/scripts/package/mkdebian
> +++ b/scripts/package/mkdebian
> @@ -163,7 +163,6 @@ while [ $# -gt 0 ]; do
>  done
>  
>  # Some variables and settings used throughout the script
> -version=$KERNELRELEASE
>  if [ "${KDEB_PKGVERSION:+set}" ]; then
>  	packageversion=$KDEB_PKGVERSION
>  else
> @@ -222,11 +221,11 @@ Build-Depends-Arch: bc, bison, flex,
>   python3:native, rsync
>  Homepage: https://www.kernel.org/
>  
> -Package: $packagename-$version
> +Package: $packagename-${KERNELRELEASE}
>  Architecture: $debarch
> -Description: Linux kernel, version $version
> +Description: Linux kernel, version ${KERNELRELEASE}
>   This package contains the Linux kernel, modules and corresponding other
> - files, version: $version.
> + files, version: ${KERNELRELEASE}.
>  EOF
>  
>  if [ "${SRCARCH}" != um ]; then
> @@ -245,11 +244,11 @@ EOF
>  if is_enabled CONFIG_MODULES; then
>  cat <<EOF >> debian/control
>  
> -Package: linux-headers-$version
> +Package: linux-headers-${KERNELRELEASE}
>  Architecture: $debarch
>  Build-Profiles: <!pkg.${sourcename}.nokernelheaders>
> -Description: Linux kernel headers for $version on $debarch
> - This package provides kernel header files for $version on $debarch
> +Description: Linux kernel headers for ${KERNELRELEASE} on $debarch
> + This package provides kernel header files for ${KERNELRELEASE} on $debarch
>   .
>   This is useful for people who need to build external modules
>  EOF
> @@ -259,11 +258,11 @@ fi
>  if is_enabled CONFIG_DEBUG_INFO; then
>  cat <<EOF >> debian/control
>  
> -Package: linux-image-$version-dbg
> +Package: linux-image-${KERNELRELEASE}-dbg
>  Section: debug
>  Architecture: $debarch
>  Build-Profiles: <!pkg.${sourcename}.nokerneldbg>
> -Description: Linux kernel debugging symbols for $version
> +Description: Linux kernel debugging symbols for ${KERNELRELEASE}
>   This package will come in handy if you need to debug the kernel. It provides
>   all the necessary debug symbols for the kernel and its modules.
>  EOF
> -- 
> 2.43.0
> 

      reply	other threads:[~2025-03-11 19:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-11 19:02 Masahiro Yamada
2025-03-11 19:19 ` Nathan Chancellor [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=20250311191900.GB1958594@ax162 \
    --to=nathan@kernel.org \
    --cc=ben@decadent.org.uk \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --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 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®