From: Ben Hutchings <ben@decadent.org.uk>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: linux-kernel@vger.kernel.org, Michal Marek <mmarek@suse.cz>,
maximilian attems <max@stro.at>,
debian-kernel@lists.debian.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 1/2] kbuild: Fix link to headers in 'make deb-pkg'
Date: Thu, 16 Feb 2012 04:45:21 +0000 [thread overview]
Message-ID: <1329367521.3048.165.camel@deadeye> (raw)
In-Reply-To: <1329323907-7696-1-git-send-email-joerg.roedel@amd.com>
[-- Attachment #1: Type: text/plain, Size: 711 bytes --]
On Wed, 2012-02-15 at 17:38 +0100, Joerg Roedel wrote:
> The Link to the kernel header files in the debian packages
> point to the original build directory. This is a bad choice
> if the packages were installed on a different machine. Fix
> this in by manually re-creating the link in the builddeb
> script.
>
> Cc: Michal Marek <mmarek@suse.cz>
> Cc: maximilian attems <max@stro.at>
> Cc: Ben Hutchings <ben@decadent.org.uk>
> Cc: debian-kernel@lists.debian.org
> Cc: linux-kbuild@vger.kernel.org
> Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>
[...]
Reviewed-by: Ben Hutchings <ben@decadent.org.uk>
--
Ben Hutchings
Beware of programmers who carry screwdrivers. - Leonard Brandwein
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-02-16 4:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 16:38 [PATCH 1/2] kbuild: Fix link to headers in 'make deb-pkg' Joerg Roedel
2012-02-15 16:38 ` [PATCH 2/2] kbuild: Only build linux-image package for UML Joerg Roedel
2012-02-16 4:49 ` Ben Hutchings
2012-02-16 21:29 ` Mattia Dongili
2012-02-24 22:56 ` Michal Marek
2012-02-16 4:45 ` Ben Hutchings [this message]
2012-02-24 22:56 ` [PATCH 1/2] kbuild: Fix link to headers in 'make deb-pkg' 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=1329367521.3048.165.camel@deadeye \
--to=ben@decadent.org.uk \
--cc=debian-kernel@lists.debian.org \
--cc=joerg.roedel@amd.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=max@stro.at \
--cc=mmarek@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).