From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: linux-sh@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Robert Love <rlove@rlove.org>
Subject: [Q] CONFIG_INOTIFY_USER doesn't get enabled upon defconfig
Date: Wed, 24 Oct 2012 12:02:13 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.1210241057590.31768@axis700.grange> (raw)
Hi all
CONFIG_INOTIFY_USER is marked default "y" in fs/notify/inotify/Kconfig,
so, I would expect it to be enabled by any make *_defconfig. However, for
some reason, this doesn't happen (e.g. with mackerel_defconfig), which
leads to non-functional udev, among others. Any idea why this could be
happening?
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
next reply other threads:[~2012-10-24 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 10:02 Guennadi Liakhovetski [this message]
2012-10-24 20:35 ` [Q] CONFIG_INOTIFY_USER doesn't get enabled upon defconfig Randy Dunlap
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=Pine.LNX.4.64.1210241057590.31768@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=rlove@rlove.org \
/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;
as well as URLs for NNTP newsgroup(s).