From: Joe Perches <joe@perches.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Matthew Dharm <mdharm-usb@one-eyed-alien.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb <linux-usb@vger.kernel.org>,
usb-storage <usb-storage@lists.one-eyed-alien.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usb: storage: Add usb_stor_dbg, reduce object size
Date: Wed, 17 Apr 2013 07:39:43 -0700 [thread overview]
Message-ID: <1366209583.28609.35.camel@joe-AO722> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1304171012270.1623-100000@iolanthe.rowland.org>
On Wed, 2013-04-17 at 10:14 -0400, Alan Stern wrote:
> On Tue, 16 Apr 2013, Joe Perches wrote:
> > Reduce the size of the objects by consolidating
> > the duplicated USB_STORAGE into a single function.
[]
> Is there any reasonable way to change this so that US_DEBUGP gets
> converted to a dev_dbg call instead of a printk call? Not including
> the device identifier in the output can be a real problem if there are
> multiple mass-storage devices in the system.
No.
There's no standardized name of a struct device *.
struct us_data *us exists for most of them but not
all. Some have a struct isd_200 *info available,
other don't have a struct device * at all.
Some or all US_DEBUGP calls would have to change
form.
Perhaps a good patch would be to convert US_DEBUGP
calls where a struct us_data * is available to
to us_stor_dbg(struct us_data *, const char *fmt, ...)
next prev parent reply other threads:[~2013-04-17 14:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 5:44 Joe Perches
2013-04-17 14:14 ` Alan Stern
2013-04-17 14:39 ` Joe Perches [this message]
2013-04-17 15:06 ` Alan Stern
2013-04-17 17:17 ` Joe Perches
2013-04-17 18:47 ` Alan Stern
2013-04-18 0:18 ` Joe Perches
2013-04-18 14:57 ` Alan Stern
2013-04-18 16:11 ` Joe Perches
2013-04-18 3:00 ` [PATCH] usb: storage: Convert US_DEBUGP to usb_stor_dbg Joe Perches
2013-04-19 17:35 ` Greg Kroah-Hartman
2013-04-19 17:44 ` Joe Perches
2013-04-19 18:44 ` [PATCH V2] " Joe Perches
2013-04-22 19:35 ` David Rientjes
2013-04-25 22:32 ` Andrew Morton
2013-04-26 8:59 ` David Rientjes
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=1366209583.28609.35.camel@joe-AO722 \
--to=joe@perches.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mdharm-usb@one-eyed-alien.net \
--cc=stern@rowland.harvard.edu \
--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
all inboxes | Powered by JetHome®