04 Aug, 2006
1 commit
-
Remove uevent dock notifications. There are no consumers
of these events at present, and uevents are likely not the
correct way to send this type of event anyway.Until I get some kind of idea if anyone in userspace cares
about dock events, I will just not send any.Signed-off-by: Kristen Carlson Accardi
Signed-off-by: Greg Kroah-Hartman
27 Jun, 2006
1 commit
-
so that userspace can be notified of dock and undock events.
Signed-off-by: Kristen Carlson Accardi
Signed-off-by: Greg Kroah-Hartman
Signed-off-by: Andrew Morton
Signed-off-by: Len Brown
28 Apr, 2006
1 commit
-
This fixes a build error for various odd combinations of CONFIG_HOTPLUG
and CONFIG_NET.Signed-off-by: Kay Sievers
Cc: Nigel Cunningham
Cc: Andrew Morton
Signed-off-by: Greg Kroah-Hartman
21 Mar, 2006
1 commit
-
Moving uevent_seqnum and uevent_helper to kobject_uevent.c
because they are used even if CONFIG_SYSFS=n
while kernel/ksysfs.c is built only if CONFIG_SYSFS=y,Signed-off-by: Jun'ichi Nomura
Signed-off-by: Greg Kroah-Hartman
23 Feb, 2006
1 commit
-
This change reverts the 033b96fd30db52a710d97b06f87d16fc59fee0f1 commit
from Kay Sievers that removed the mount/umount uevents from the kernel.
Some older versions of HAL still depend on these events to detect when a
new device has been mounted. These events are not correctly emitted,
and are broken by design, and so, should not be relied upon by any
future program. Instead, the /proc/mounts file should be polled to
properly detect this kind of event.A feature-removal-schedule.txt entry has been added, noting when this
interface will be removed from the kernel.Signed-off-by: Greg Kroah-Hartman
07 Feb, 2006
1 commit
-
The buffer used for kobject uevent is too small for some of the events generated
by the input layer. Bump it to 2k.Signed-off-by: Benjamin Herrenschmidt
Signed-off-by: Greg Kroah-Hartman
05 Jan, 2006
5 commits
-
lib/lib.a(kobject_uevent.o)(.text+0x25f): In function `kobject_uevent':
: undefined reference to `__alloc_skb'
lib/lib.a(kobject_uevent.o)(.text+0x2a1): In function `kobject_uevent':
: undefined reference to `skb_over_panic'
lib/lib.a(kobject_uevent.o)(.text+0x31d): In function `kobject_uevent':
: undefined reference to `skb_over_panic'
lib/lib.a(kobject_uevent.o)(.text+0x356): In function `kobject_uevent':
: undefined reference to `netlink_broadcast'
lib/lib.a(kobject_uevent.o)(.init.text+0x9): In function `kobject_uevent_init':
: undefined reference to `netlink_kernel_create'
make: *** [.tmp_vmlinux1] Error 1Netlink is unconditionally enabled if CONFIG_NET, so that's OK.
kobject_uevent.o is compiled even if !CONFIG_HOTPLUG, which is lazy.
Let's compound the sin.
Signed-off-by: Andrew Morton
Signed-off-by: Greg Kroah-Hartman -
Leave the overloaded "hotplug" word to susbsystems which are handling
real devices. The driver core does not "plug" anything, it just exports
the state to userspace and generates events.Signed-off-by: Kay Sievers
Signed-off-by: Greg Kroah-Hartman -
The distinction between hotplug and uevent does not make sense these
days, netlink events are the default.udev depends entirely on netlink uevents. Only during early boot and
in initramfs, /sbin/hotplug is needed. So merge the two functions and
provide only one interface without all the options.The netlink layer got a nice generic interface with named slots
recently, which is probably a better facility to plug events for
subsystem specific events.
Also the new poll() interface to /proc/mounts is a nicer way to
notify about changes than sending events through the core.
The uevents should only be used for driver core related requests to
userspace now.Signed-off-by: Kay Sievers
Signed-off-by: Greg Kroah-Hartman -
The names of these events have been confusing from the beginning
on, as they have been more like claim/release events. We needed these
events for noticing HAL if storage devices have been mounted.Thanks to Al, we have the proper solution now and can poll()
/proc/mounts instead to get notfied about mount tree changes.Signed-off-by: Kay Sievers
Signed-off-by: Greg Kroah-Hartman -
It makes zero sense to have hotplug, but not the netlink
events enabled today. Remove this option and merge the
kobject_uevent.h header into the kobject.h header file.Signed-off-by: Kay Sievers
Signed-off-by: Greg Kroah-Hartman
29 Oct, 2005
2 commits
-
This patch changes trough to through in a comment in kobject_uevent.c.
Signed-off-by: Greg Kroah-Hartman
28 Oct, 2005
1 commit
-
Signed-off-by: Al Viro
Signed-off-by: Linus Torvalds
30 Aug, 2005
4 commits
-
Signed-off-by: Patrick McHardy
Signed-off-by: David S. Miller -
Signed-off-by: Patrick McHardy
Signed-off-by: David S. Miller -
netlink_broadcast users must initialize NETLINK_CB(skb).dst_groups to the
destination group mask for netlink_recvmsg.Signed-off-by: Patrick McHardy
Signed-off-by: David S. Miller -
- Remove bogus code for compiling netlink as module
- Add module refcounting support for modules implementing a netlink
protocol
- Add support for autoloading modules that implement a netlink protocol
as soon as someone opens a socket for that protocolSigned-off-by: Harald Welte
Signed-off-by: David S. Miller
21 Jun, 2005
2 commits
-
kobject: make kobject's name const char * since users should not
attempt to change it (except by calling kobject_rename).Signed-off-by: Dmitry Torokhov
Signed-off-by: Greg Kroah-Hartman -
kobject: kobject_hotplug should use kobject_name() instead of
accessing kobj->name directly since for objects with
long names it can contain garbage.Signed-off-by: Dmitry Torokhov
Signed-off-by: Greg Kroah-Hartman
17 Apr, 2005
1 commit
-
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.Let it rip!
