Re: [-mm3 PATCH] (Retry) Check the return value of kobject_add and etc.

On Tue, 10 Apr 2007 15:18:15 -0700,
Andrew Morton <[email protected]> wrote:

> Note that I changed it to not send the KOBJ_REMOVE if we didn't send a
> KOBJ_ADD.

The whole part_uevent_suppress stuff is not really nice, causing the
code to use a lot of kobject_{init,add} and kobject_{del,put} instead
of kobject_register and kobject_unregister. Looking at
driver-class/block-device.patch in Greg's tree, it should be possible
to use something like the uevent_filter stuff after block has been
converted.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Re: [-mm3 PATCH] (Retry) Check the return value of kobject_add and etc.
    • From: Cornelia Huck <[email protected]>
  • Re: [-mm3 PATCH] (Retry) Check the return value of kobject_add and etc.
    • From: WANG Cong <[email protected]>
  • Re: [-mm3 PATCH] (Retry) Check the return value of kobject_add and etc.
    • From: Andrew Morton <[email protected]>

• Prev by Date: evdev* devices change major/minors after suspend/resume (udev?)
• Next by Date: Re: [PATCH, take4] FUTEX : new PRIVATE futexes
• Previous by thread: Re: [-mm3 PATCH] (Retry) Check the return value of kobject_add and etc.
• Next by thread: [PATCH] Build break on ppc64 for 2.6.21-rc6-mm1
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]