mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vitaliy Ivanov" <vitalivanov@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: USB adutux device number
Date: Tue, 15 May 2007 15:05:41 +0300	[thread overview]
Message-ID: <35fbaa3e0705150505i5f85f1a0rade73340cd60f690@mail.gmail.com> (raw)
In-Reply-To: <35fbaa3e0705140910s19feac4bnd71a80f25dc4753c@mail.gmail.com>

Did any of USB fellows has a chance to look at this issue?

It can be critical to customers as this 67 minor number is listed in
the driver code only and not all of them going through the code.

-- Vitaliy


On 5/14/07, Vitaliy Ivanov <vitalivanov@gmail.com> wrote:
> Hello,
>
> I'm not sure if it's correct place to deal with the issue.
>
> In Documentation/devices.txt there is no info about adutux driver that
> is included in the kernel:
> ...
>                  65 = /dev/usb/usblcd   USBLCD Interface (info@usblcd.de)
>                  66 = /dev/usb/cpad0    Synaptics cPad (mouse/LCD)
>                  96 = /dev/usb/hiddev0  1st USB HID device
>                     ...
> ...
>
> The driver itself includes the following (drivers/usb/misc/adutux.c):
>
> #ifdef CONFIG_USB_DYNAMIC_MINORS
> #define ADU_MINOR_BASE  0
> #else
> #define ADU_MINOR_BASE  67
> #endif
>
> We need to update Documentation/devices.txt with this information. The
> number of devices is 16.
>
> I found an old mail tread for this:
> http://www.uwsg.iu.edu/hypermail/linux/kernel/0609.3/2173.html
> But I don't see anything related to adu devices in devices.txt at all.
>
> Please let me know what is the reason of this. If needed I will create
> a patch for this.
>
> -- V
>

  reply	other threads:[~2007-05-15 12:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-14 16:10 Vitaliy Ivanov
2007-05-15 12:05 ` Vitaliy Ivanov [this message]
2007-06-01 13:35   ` 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=35fbaa3e0705150505i5f85f1a0rade73340cd60f690@mail.gmail.com \
    --to=vitalivanov@gmail.com \
    --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®