Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] force devtmpfs and inotify kernel option when udev is used as dev handler
Date: Wed, 08 Jan 2014 22:28:59 +0100	[thread overview]
Message-ID: <87ha9enox0.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1389188913-15173-1-git-send-email-jeremy.rosen@openwide.fr> ("Jérémy Rosen"'s message of "Wed, 8 Jan 2014 14:48:33 +0100")

>>>>> "J?r?my" == J?r?my Rosen <jeremy.rosen@openwide.fr> writes:

 > Signed-off-by: J?r?my Rosen <jeremy.rosen@openwide.fr>
 > ---
 > patch suggested by Thomas Petazzoni

 > I also added devtmpfs because it's documented as needed but wasn't enforced
 > ---
 >  linux/linux.mk | 4 ++++
 >  1 file changed, 4 insertions(+)

 > diff --git a/linux/linux.mk b/linux/linux.mk
 > index fa8aa0c..2482952 100644
 > --- a/linux/linux.mk
 > +++ b/linux/linux.mk
 > @@ -185,6 +185,10 @@ 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)
 > +		$(call KCONFIG_ENABLE_OPT,CONFIG_DEVTMPFS,$(@D)/.config)
 > +		$(call KCONFIG_ENABLE_OPT,CONFIG_DEVTMPFS_MOUNT,$(@D)/.config))

Committed with the indentation fixed and the unneeded devtmpfs handling
removed, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2014-01-08 21:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08 13:48 [Buildroot] [PATCH] force devtmpfs and inotify kernel option when udev is used as dev handler Jérémy Rosen
2014-01-08 14:13 ` Danomi Manchego
2014-01-08 15:42   ` Jeremy Rosen
2014-01-08 15:45 ` Thomas Petazzoni
2014-01-09  8:03   ` Jeremy Rosen
2014-01-08 21:28 ` 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=87ha9enox0.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