From: Pete Zaitcev <zaitcev@redhat.com>
To: Phil Dibowitz <phil@ipom.com>
Cc: linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net,
usb-storage@lists.one-eyed-alien.net, zaitcev@redhat.com
Subject: Re: RFC drivers/usb/storage/libusual
Date: Fri, 30 Sep 2005 17:26:00 -0700 [thread overview]
Message-ID: <20050930172600.298b7cac.zaitcev@redhat.com> (raw)
In-Reply-To: <433CE491.90305@ipom.com>
On Fri, 30 Sep 2005 00:09:05 -0700, Phil Dibowitz <phil@ipom.com> wrote:
> A quick look over the patch shows that there are now two kinds of
> unusual_dev entries: unusual_dev() and unusual_dev_fl(), where the
> latter is for entries that don't need to specify SC or PR (i.e., just
> had US_SC_DEVICE, US_PR_DEVICE in them). While I think that's a
> reasonable change, it's not clear to me why that's useful to the rest of
> the patch, or it's just making unusual_devs.h artificially shorter?
Greg asked that too and I skipped his question because I needed an
explanation. So here it is now.
I thought that the match list for USB core and the shadow list that
usb-storage had were separate. So, libusual receives the first but
not the second, which remains in usb-storage. Once they are split
like that, I thought it unsafe to continue to use an index to
correlate them, so I added extra fields into the list of information
specific list to usb-storage, for matching. These fields use more
memory, so I thought it would cost nothing to move flags over
into driver_info. The resultant savings make usb-storage somewhat
shorter than it was before. It is shorter even when libusual is
configured off. This is because the second list is about twice
shorter now.
I can drop that part of the patch, I just thought it would be safer.
If you prefer that, I would suggest moving "normal" devices at the
bottom of the list into the unusual_devs.h, to make sure that
indexes stay the same. In such case, we won't need dropping commas.
-- Pete
prev parent reply other threads:[~2005-10-01 0:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 3:55 RFC drivers/usb/storage/libusual Pete Zaitcev
2005-09-28 8:52 ` [linux-usb-devel] " Greg KH
2005-09-28 19:40 ` Alan Stern
2005-09-29 0:01 ` Pete Zaitcev
2005-10-10 21:15 ` Rusty Russell
2005-10-07 7:24 ` Pete Zaitcev
2005-10-07 14:41 ` [usb-storage] " Alan Stern
2005-10-08 7:35 ` Pete Zaitcev
2005-10-08 15:17 ` Alan Stern
2005-10-08 21:01 ` usb: drivers/usb/storage/libusual Pete Zaitcev
2005-10-09 2:14 ` [usb-storage] " Matthew Dharm
2005-10-09 8:09 ` Pete Zaitcev
2005-09-28 16:56 ` [linux-usb-devel] RFC drivers/usb/storage/libusual Alan Stern
2005-09-29 2:21 ` Pete Zaitcev
2005-09-30 7:09 ` [linux-usb-devel] " Phil Dibowitz
2005-10-01 0:26 ` Pete Zaitcev [this message]
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=20050930172600.298b7cac.zaitcev@redhat.com \
--to=zaitcev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=phil@ipom.com \
--cc=usb-storage@lists.one-eyed-alien.net \
/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;
as well as URLs for NNTP newsgroup(s).