All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] udev: mention dependancy on inotify
Date: Wed, 8 Jan 2014 06:23:44 +0800	[thread overview]
Message-ID: <20140108062344.362a979d@skate> (raw)
In-Reply-To: <20140107203417.C734D9BEF5@busybox.osuosl.org>

Dear Peter Korsgaard,

On Tue, 7 Jan 2014 21:33:34 +0100, Peter Korsgaard wrote:

> -	  udev requires a Linux kernel >= 2.6.34: it relies on devtmpfs.
> +	  udev requires a Linux kernel >= 2.6.34: it relies on devtmpfs
> +	  and inotify.

Then, maybe we need something like:

diff --git a/linux/linux.mk b/linux/linux.mk
index fa8aa0c..ab25fe9 100644
--- a/linux/linux.mk
+++ b/linux/linux.mk
@@ -185,6 +185,8 @@ define LINUX_CONFIGURE_CMDS
                $(call KCONFIG_ENABLE_OPT,CONFIG_DEVTMPFS_MOUNT,$(@D)/.config))
        $(if $(BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_MDEV),
                $(call KCONFIG_SET_OPT,CONFIG_UEVENT_HELPER_PATH,\"/sbin/mdev\",$(@D)/.config))
+       $(if $(BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_UDEV),
+               $(call KCONFIG_ENABLE_OPT,CONFIG_INOTIFY_USER,$(@D)/.config))
        $(if $(BR2_PACKAGE_KTAP),
                $(call KCONFIG_ENABLE_OPT,CONFIG_DEBUG_FS,$(@D)/.config)
                $(call KCONFIG_ENABLE_OPT,CONFIG_EVENT_TRACING,$(@D)/.config)

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-01-07 22:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-07 20:33 [Buildroot] [git commit] udev: mention dependancy on inotify Peter Korsgaard
2014-01-07 22:23 ` Thomas Petazzoni [this message]
2014-01-08  8:24   ` Jeremy Rosen

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=20140108062344.362a979d@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 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.