From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 0/2] Checking whether a certain CONFIG_* is set
Date: Wed, 19 Aug 2015 22:23:03 +0200 [thread overview]
Message-ID: <20150819222303.2f2c17ce@free-electrons.com> (raw)
In-Reply-To: <20150819192157.GC13372@free.fr>
Dear Yann E. MORIN,
On Wed, 19 Aug 2015 21:21:57 +0200, Yann E. MORIN wrote:
> > We already do your second item.
>
> No, we are not allowing any random package to set kernel options.
No, we do it the other way around: linux.mk tweaks the kernel options
depending on which packages are selected.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-08-19 20:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 16:50 [Buildroot] xtables-addons does not build for arm kernel 4.1.4 Jan Viktorin
2015-08-17 21:52 ` Peter Korsgaard
2015-08-17 22:35 ` Jan Viktorin
2015-08-19 13:14 ` [Buildroot] [PATCH v1 0/2] Checking whether a certain CONFIG_* is set Jan Viktorin
2015-08-19 13:14 ` [Buildroot] [PATCH v1 1/2] pkg-utils: Define KCONFIG_ASSERT_OPT macro Jan Viktorin
2015-08-19 19:16 ` Yann E. MORIN
2015-08-19 13:14 ` [Buildroot] [PATCH v1 2/2] xtables-addons: test CONFIG_MODULES=y in the kernel Jan Viktorin
2015-08-19 17:46 ` [Buildroot] [PATCH v1 0/2] Checking whether a certain CONFIG_* is set Thomas Petazzoni
2015-08-19 19:05 ` Yann E. MORIN
2015-08-19 19:08 ` Thomas Petazzoni
2015-08-19 19:21 ` Yann E. MORIN
2015-08-19 20:23 ` Thomas Petazzoni [this message]
2015-08-19 21:05 ` Peter Korsgaard
2015-08-21 13:22 ` Yann E. MORIN
2015-08-21 13:41 ` Jeremy Rosen
2015-08-21 20:28 ` Peter Korsgaard
2015-08-21 21:05 ` Yann E. MORIN
2015-08-21 22:17 ` Peter Korsgaard
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=20150819222303.2f2c17ce@free-electrons.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.