From: Lukasz Stelmach <stlman@poczta.fm>
To: linux-kernel@vger.kernel.org
Subject: [patch] CONFIG_KOBJECT_UEVENTS in 2.6.15
Date: Sun, 29 Jan 2006 13:35:19 +0100 [thread overview]
Message-ID: <43DCB687.1090605@poczta.fm> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 620 bytes --]
Greetings.
IMHO since CONFIG_KOBJECT_UEVENT depends on CONFIG_EMBEDDED it should be
placed in this menu. Now it is in "General setup", what might cause, or
I am such a dumb, some confusion because it is invisible "without any
reason" until C_E is. Here you are a patch that, let me say, fixes the
Kconfig file.
--
Było mi bardzo miło. Czwarta pospolita klęska, [...]
>Łukasz< Już nie katolicka lecz złodziejska. (c)PP
----------------------------------------------------------------------
Kobiety i samochody... piekne! >>> http://link.interia.pl/f18f5
[-- Attachment #1.2: kconfig.diff --]
[-- Type: text/x-patch, Size: 2138 bytes --]
--- /tmp/Kconfig-2.6.15-orig 2006-01-29 13:22:33.000000000 +0100
+++ /tmp/Kconfig-2.6.15 2006-01-29 13:25:10.000000000 +0100
@@ -205,25 +205,6 @@
modules require HOTPLUG functionality, but a module built
outside the kernel tree does. Such modules require Y here.
-config KOBJECT_UEVENT
- bool "Kernel Userspace Events" if EMBEDDED
- depends on NET
- default y
- help
- This option enables the kernel userspace event layer, which is a
- simple mechanism for kernel-to-user communication over a netlink
- socket.
- The goal of the kernel userspace events layer is to provide a simple
- and efficient events system, that notifies userspace about kobject
- state changes. This will enable applications to just listen for
- events instead of polling system devices and files.
- Hotplug events (kobject addition and removal) are also available on
- the netlink socket in addition to the execution of /sbin/hotplug if
- CONFIG_HOTPLUG is enabled.
-
- Say Y, unless you are building a system requiring minimal memory
- consumption.
-
config IKCONFIG
bool "Kernel .config support"
---help---
@@ -362,6 +343,25 @@
option replaces shmem and tmpfs with the much simpler ramfs code,
which may be appropriate on small systems without swap.
+config KOBJECT_UEVENT
+ bool "Kernel Userspace Events" if EMBEDDED
+ depends on NET
+ default y
+ help
+ This option enables the kernel userspace event layer, which is a
+ simple mechanism for kernel-to-user communication over a netlink
+ socket.
+ The goal of the kernel userspace events layer is to provide a simple
+ and efficient events system, that notifies userspace about kobject
+ state changes. This will enable applications to just listen for
+ events instead of polling system devices and files.
+ Hotplug events (kobject addition and removal) are also available on
+ the netlink socket in addition to the execution of /sbin/hotplug if
+ CONFIG_HOTPLUG is enabled.
+
+ Say Y, unless you are building a system requiring minimal memory
+ consumption.
+
config CC_ALIGN_FUNCTIONS
int "Function alignment" if EMBEDDED
default 0
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next reply other threads:[~2006-01-29 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-29 12:35 Lukasz Stelmach [this message]
2006-01-29 19:06 ` Greg KH
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=43DCB687.1090605@poczta.fm \
--to=stlman@poczta.fm \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®