All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 1/1] ktap: new package
Date: Tue, 10 Dec 2013 14:01:45 +0100 (CET)	[thread overview]
Message-ID: <1675197757.16219192.1386680505536.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <20131210125526.GA5876@ad.chargestorm.se>

> 
> > It would be good if we could automatically enable the needed kernel
> > features when ktap is enabled, similar to how we do for E.G.
> > devtmpfs.
> 
> Sure, that would be an idea.
> 
> I could take a look at that, as long as it's OK with everyone that
> enabling ktap might change the kernel config. (Though, it'll be
> pretty
> deterministic anyway)...
> 
> > But that can be done as a followup patch, so committed - Thanks.
> 

two remarks

1) the usual problem with that idea is that if the kernel is externally
built, you can't do that (you don't even know if/where the config is)

2) I'd rather have it works similar to other dependancies, i.e having
the option removed and a comment telling me what I need to enable to 
have ktap available.

I recently had a similar problem with udev needing inotify, so the 
problem of the plumbing layer relying on some specific kernel feature
is probably a more generic problem... maybe a config option telling
kconfig where the kernel is ? That would be tricky with the way 
kconfig works, but that would be nice...

  reply	other threads:[~2013-12-10 13:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-10 11:59 [Buildroot] [PATCH v5 1/1] ktap: new package Anders Darander
2013-12-10 12:35 ` Peter Korsgaard
2013-12-10 12:55   ` Anders Darander
2013-12-10 13:01     ` Jeremy Rosen [this message]
2013-12-10 13:39       ` Peter Korsgaard
2013-12-10 14:36         ` Thomas De Schampheleire
2013-12-10 14:42           ` Peter Korsgaard
2013-12-10 14:49             ` Thomas De Schampheleire
2013-12-10 16:54               ` Arnout Vandecappelle
2013-12-10 20:50                 ` 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=1675197757.16219192.1386680505536.JavaMail.root@openwide.fr \
    --to=jeremy.rosen@openwide.fr \
    --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.