mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dan Williams" <dan.j.williams@intel.com>
To: "Greg KH" <greg@kroah.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"Kay Sievers" <kay.sievers@vrfy.org>,
	linux-usb@vger.kernel.org
Subject: Re: [PATCH mm] sysfs: add /sys/dev/usb to handle CONFIG_USB_DEVICE_CLASS=y
Date: Thu, 17 Apr 2008 21:59:34 -0700	[thread overview]
Message-ID: <e9c3a7c20804172159x16554078i6d5c9097eeadc91c@mail.gmail.com> (raw)
In-Reply-To: <20080418032146.GA8754@kroah.com>

On Thu, Apr 17, 2008 at 8:21 PM, Greg KH <greg@kroah.com> wrote:
> On Thu, Apr 17, 2008 at 07:11:03PM -0700, Dan Williams wrote:
>
> > The deprecated config option CONFIG_USB_DEVICE_CLASS causes class devices
>  > with duplicate major:minor numbers to be registered.  In effect they
>  > represent a usb specific address space for major:minor numbers so add 'usb'
>  > as a directory along side 'block' and 'char'.
>
>  Hm, no they do not, they are not a new address space, we are just
>  reusing them as the other user wasn't using them, and the code is
>  deprecated and will be removed eventually.  Neither of these char
>  devices are really hooked up to anything within the kernel, so it
>  doesn't matter yet.
>
>  I wonder how many other duplicates we have floating around...
>

Hm, so how about making this an opt-in capability of the class?  At
device_add() time the class is queried to see if a link should be
created in /sys/dev/block or /sys/dev/char?  Although, this leads to
inconsistent coverage.  But maybe that does not matter as many of
these character devices do not have interesting attributes to be
accessed?  Sigh, I am beginning to wonder if the character device side
of this capability is a solution looking for a problem...

Ideas?

>  thanks,
>
>  greg k-h
>

Thanks,
Dan

  reply	other threads:[~2008-04-18  4:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-18  2:11 Dan Williams
2008-04-18  3:00 ` Greg KH
2008-04-18  3:08 ` Andrew Morton
2008-04-18  3:44   ` Dan Williams
2008-04-18  3:21 ` Greg KH
2008-04-18  4:59   ` Dan Williams [this message]
2008-04-18  7:54     ` Kay Sievers
2008-04-18 16:37       ` Dan Williams

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=e9c3a7c20804172159x16554078i6d5c9097eeadc91c@mail.gmail.com \
    --to=dan.j.williams@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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®