From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] i2c-tools: Adds check of i2c kernel option
Date: Tue, 4 Aug 2015 15:52:22 +0200 [thread overview]
Message-ID: <20150804155222.580ff18e@free-electrons.com> (raw)
In-Reply-To: <96448357.4733141.1438695534642.JavaMail.root@openwide.fr>
Denis,
On Tue, 4 Aug 2015 15:38:54 +0200 (CEST), Denis Thulin wrote:
> I understand that this is a mistake for kernel options.
> But could patch [1/2] be useful for the other kconfig packages ?
> I think it would be useful to know options of busybox when building
> packages.
I am not sure for what reasons other packages would need to know the
Busybox options that are enabled.
> Would it not be a better thing for all packages to provide a list
> of kernel options they need and for LINUX_KCONFIG_FIXUP_CMDS
> to select those options rather than using lots of if blocks ?
Could be, yes. Not sure how that would work, though. We want to keep
this list of condition relatively short, and not encourage adding
millions of interactions between user space dependencies and kernel
options.
> That list could also be exported so that people using a custom kernel
> would know which options Buildroot would have selected had they used
> the default kernel.
People using a custom kernel "know what they are doing", so I'm not too
interested in solving this particular use case.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-08-04 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 12:27 [Buildroot] [PATCH 0/2] pkg-kconfig now loads kconfig variables Denis THULIN
2015-08-04 12:27 ` [Buildroot] [PATCH 1/2] kconfig: Can now use variables outside of package Denis THULIN
2015-08-04 12:27 ` [Buildroot] [PATCH 2/2] i2c-tools: Adds check of i2c kernel option Denis THULIN
2015-08-04 12:45 ` Thomas Petazzoni
2015-08-04 13:38 ` Denis Thulin
2015-08-04 13:52 ` 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=20150804155222.580ff18e@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox