From: Michal Marek <mmarek@suse.cz>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: linux-kbuild@vger.kernel.org, maximilian attems <max@stro.at>,
Ben Hutchings <ben@decadent.org.uk>
Subject: Re: [PATCH] Provide version number for Debian firmware package
Date: Tue, 13 Aug 2013 22:20:56 +0200 [thread overview]
Message-ID: <520A9528.4000309@suse.cz> (raw)
In-Reply-To: <1376250919-13886-1-git-send-email-xypron.glpk@gmx.de>
Dne 11.8.2013 21:55, Heinrich Schuchardt napsal(a):
> scripts/package/builddeb is used to create Debian packages.
> Currently the firmware package always gets the same version number
> irrespective of the Kernel version.
> The paths inside the firmware package depend on the Kernel
> version.
>
> With the patch supplied the Kernel version becomes part of the
> Debian firmware package number.
Ben, Max, is this how the official linux-firmware-image package is built
in Debian? The change makes sense to me.
Michal
>
> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> ---
> scripts/package/builddeb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/package/builddeb b/scripts/package/builddeb
> index acb8650..4ca6111 100644
> --- a/scripts/package/builddeb
> +++ b/scripts/package/builddeb
> @@ -79,7 +79,7 @@ fwdir="$objtree/debian/fwtmp"
> kernel_headers_dir="$objtree/debian/hdrtmp"
> libc_headers_dir="$objtree/debian/headertmp"
> packagename=linux-image-$version
> -fwpackagename=linux-firmware-image
> +fwpackagename=linux-firmware-image-$version
> kernel_headers_packagename=linux-headers-$version
> libc_headers_packagename=linux-libc-dev
>
>
next prev parent reply other threads:[~2013-08-13 20:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 19:55 [PATCH] Provide version number for Debian firmware package Heinrich Schuchardt
2013-08-13 20:20 ` Michal Marek [this message]
2013-08-13 21:02 ` Ben Hutchings
2013-08-14 18:15 ` maximilian attems
2013-08-15 16:02 ` Michal Marek
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=520A9528.4000309@suse.cz \
--to=mmarek@suse.cz \
--cc=ben@decadent.org.uk \
--cc=linux-kbuild@vger.kernel.org \
--cc=max@stro.at \
--cc=xypron.glpk@gmx.de \
/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