From: Joerg Roedel <joro@8bytes.org>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
debian-kernel@lists.debian.org, Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org, cpufreq@vger.kernel.org,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Viresh Kumar <viresh.kumar@linaro.org>,
Linux PM List <linux-pm@lists.linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next <linux-next@vger.kernel.org>
Subject: Re: [RFC PATCH] kbuild: Build linux-tools package with 'make deb-pkg'
Date: Wed, 10 Apr 2013 09:57:24 +0200 [thread overview]
Message-ID: <20130410075724.GK6858@8bytes.org> (raw)
In-Reply-To: <CA+icZUU=SdiaPBqabf0miOM1Arsc=PjHQbY4GpaDiM4=Fbp73A@mail.gmail.com>
Hi Sedat,
On Wed, Apr 10, 2013 at 09:41:55AM +0200, Sedat Dilek wrote:
> [ CCing some involved maintainers and MLs ]
>
> Hi Joerg,
>
> what is the status of your proposal patch?
> Is this [1] the last version you posted?
Yes, this looks like the latest version. As far as I remember I didn't
get feedback on it and had not time to work further on the patch.
There are also problems with building a generic linux-tools package. One
is that the packages need to look differently for Debian and Ubuntu. The
other problem is that it may break automated x-compile builds.
Joerg
next prev parent reply other threads:[~2013-04-10 7:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 7:41 [RFC PATCH] kbuild: Build linux-tools package with 'make deb-pkg' Sedat Dilek
2013-04-10 7:57 ` Joerg Roedel [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-16 18:57 Joerg Roedel
2012-02-17 3:16 ` Ben Hutchings
2012-02-17 3:46 ` Ben Hutchings
2012-02-23 11:17 ` Joerg Roedel
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=20130410075724.GK6858@8bytes.org \
--to=joro@8bytes.org \
--cc=ben@decadent.org.uk \
--cc=cpufreq@vger.kernel.org \
--cc=debian-kernel@lists.debian.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mmarek@suse.cz \
--cc=rjw@sisk.pl \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=viresh.kumar@linaro.org \
/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).