From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3 v2] linux: do not always depend on host-lzop
Date: Tue, 4 Mar 2014 19:19:25 +0100 [thread overview]
Message-ID: <20140304191925.50aaf715@skate> (raw)
In-Reply-To: <20140303222317.795950dd@skate>
Hello,
On Mon, 3 Mar 2014 22:23:17 +0100, Thomas Petazzoni wrote:
> Dear Yann E. MORIN,
>
> On Sat, 8 Feb 2014 17:26:03 +0100, Yann E. MORIN wrote:
>
> > Here is a small series that makes Linux not always depend on host-lzop,
> > and also cleans up a little bit the linux.mk.
>
> Series applied, thanks.
And I've reverted it because it simply cannot work with internal
defconfig of the kernel, since they are only available after the kernel
has been extracted, which is too late to declare whether we need the
host-lzop dependency or not.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-03-04 18:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 16:26 [Buildroot] [PATCH 0/3 v2] linux: do not always depend on host-lzop Yann E. MORIN
2014-02-08 16:26 ` [Buildroot] [PATCH 1/3] packages infra: add function to get a Kconfig option Yann E. MORIN
2014-02-08 16:26 ` [Buildroot] [PATCH 2/3] linux: only depend on host-lzop if needed Yann E. MORIN
2014-02-08 16:26 ` [Buildroot] [PATCH 3/3] linux: check the configuration file exists Yann E. MORIN
2014-03-03 21:23 ` [Buildroot] [PATCH 0/3 v2] linux: do not always depend on host-lzop Thomas Petazzoni
2014-03-04 18:19 ` Thomas Petazzoni [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=20140304191925.50aaf715@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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