Re: [patch 0/8] Nesting class_device patches that actually work

On 10/14/05, Christoph Hellwig <[email protected]> wrote:
> NACK.  The whole point of classes is to have common attributes and
> behaviours over a set of devices.  There's much more than the dev
> attribute to them.  Please just fix the input code to get their
> semantics right instead.
>

What kind of changes would you like to see in the input system?
Currently it maps perfectly well on to what we have in sysfs (using
pair of input and input_dev classes), it is just that we do not really
like the general sysfs structure and would like to improve it.

--
Dmitry
-
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:
  • [patch 0/8] Nesting class_device patches that actually work
    • From: Greg KH <[email protected]>
  • Re: [patch 0/8] Nesting class_device patches that actually work
    • From: Christoph Hellwig <[email protected]>

• Prev by Date: Reiser4 mounting problem on ARM
• Next by Date: [PATCH] sh-sci.c sci_start_tx error
• Previous by thread: Re: [patch 0/8] Nesting class_device patches that actually work
• Next by thread: [PATCH] yealink driver: fix input patameter validations
• 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]