Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux: don't automatically set uevent_helper with mdev /dev management
Date: Sun, 09 Feb 2014 22:53:09 +0100	[thread overview]
Message-ID: <87ioso0x8a.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <769563a34e142e85ec4c.1391761259@argentina> (Thomas De Schampheleire's message of "Fri, 07 Feb 2014 09:20:59 +0100")

>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin@gmail.com> writes:

 > When mdev /dev management is chosen in the buildroot configuration, the
 > Linux configuration is updated automatically to set option
 > CONFIG_UEVENT_HELPER_PATH to "/sbin/mdev". However, the help text of this
 > option explicitly recommends not setting this option due to large
 > performance impact during boot (experienced first hand by the reporter ?nd
 > author).

 > The mdev startup script S10mdev already sets the helper during userspace
 > boot, which will make sure mdev is working correctly.

 > Fixes bug #6596: https://bugs.busybox.net/show_bug.cgi?id=6596

 > Reported-by: Andreas Koop <andreas.koop@zf.com>
 > Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>

Committed, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2014-02-09 21:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-07  8:20 [Buildroot] [PATCH] linux: don't automatically set uevent_helper with mdev /dev management Thomas De Schampheleire
2014-02-07 18:11 ` Yann E. MORIN
2014-02-07 20:50 ` Peter Korsgaard
2014-02-07 21:00   ` Thomas De Schampheleire
2014-02-07 21:05     ` Peter Korsgaard
2014-02-07 21:16       ` Thomas De Schampheleire
2014-02-08 20:51         ` Peter Korsgaard
2014-02-08 21:06           ` Thomas De Schampheleire
2014-02-09 21:52             ` Peter Korsgaard
2014-02-09 21:53 ` Peter Korsgaard [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=87ioso0x8a.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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