From: David Brownell <david-b@pacbell.net>
To: Julia Lawall <julia@diku.dk>, Alan Stern <stern@rowland.harvard.edu>
Cc: gregkh@suse.de, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 10/13] drivers/usb/gadget: use USB API functions rather than constants
Date: Mon, 29 Dec 2008 18:14:49 +0000 [thread overview]
Message-ID: <200812291014.49779.david-b@pacbell.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0812291628100.9555@pc-004.diku.dk>
On Monday 29 December 2008, Julia Lawall wrote:
> > > +#include <linux/usb.h>
> > > #include <linux/usb/ch9.h>
> > > #include <linux/usb/gadget.h>
> >
> > While there's nothing wrong with this part of the patch,
Not so; there *is* something wrong in requiring the
peripheral side support to use a host side header.
> > it hardly
> > seems necessary. Was there any reason for including it?
>
> The new functions are defined in usb.h. I have added the include in
> this file and in the file epautoconf.c that this file includes. If it is
> removed from both, then the code does not compile (after make
> allyesconfig):
Those functions were supposed to go into <linux/usb/ch9.h>, as
I recall, since they weren't specific to the host side stack.
Having them added to the wrong file is surely part of why
they've only been used by host side drivers. :)
- Dave
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: David Brownell <david-b@pacbell.net>
To: Julia Lawall <julia@diku.dk>, Alan Stern <stern@rowland.harvard.edu>
Cc: gregkh@suse.de, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 10/13] drivers/usb/gadget: use USB API functions rather than constants
Date: Mon, 29 Dec 2008 10:14:49 -0800 [thread overview]
Message-ID: <200812291014.49779.david-b@pacbell.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0812291628100.9555@pc-004.diku.dk>
On Monday 29 December 2008, Julia Lawall wrote:
> > > +#include <linux/usb.h>
> > > #include <linux/usb/ch9.h>
> > > #include <linux/usb/gadget.h>
> >
> > While there's nothing wrong with this part of the patch,
Not so; there *is* something wrong in requiring the
peripheral side support to use a host side header.
> > it hardly
> > seems necessary. Was there any reason for including it?
>
> The new functions are defined in usb.h. I have added the include in
> this file and in the file epautoconf.c that this file includes. If it is
> removed from both, then the code does not compile (after make
> allyesconfig):
Those functions were supposed to go into <linux/usb/ch9.h>, as
I recall, since they weren't specific to the host side stack.
Having them added to the wrong file is surely part of why
they've only been used by host side drivers. :)
- Dave
next prev parent reply other threads:[~2008-12-29 18:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 10:22 [PATCH 10/13] drivers/usb/gadget: use USB API functions rather than Julia Lawall
2008-12-29 10:22 ` [PATCH 10/13] drivers/usb/gadget: use USB API functions rather than constants Julia Lawall
2008-12-29 15:27 ` [PATCH 10/13] drivers/usb/gadget: use USB API functions rather Alan Stern
2008-12-29 15:27 ` [PATCH 10/13] drivers/usb/gadget: use USB API functions rather than constants Alan Stern
2008-12-29 15:35 ` [PATCH 10/13] drivers/usb/gadget: use USB API functions rather Julia Lawall
2008-12-29 15:35 ` [PATCH 10/13] drivers/usb/gadget: use USB API functions rather than constants Julia Lawall
2008-12-29 18:14 ` David Brownell [this message]
2008-12-29 18:14 ` David Brownell
2008-12-29 16:13 ` [PATCH 10/13] drivers/usb/gadget: use USB API functions rather Alan Stern
2008-12-29 16:13 ` [PATCH 10/13] drivers/usb/gadget: use USB API functions rather than constants Alan Stern
2008-12-29 16:18 ` [PATCH 10/13] drivers/usb/gadget: use USB API functions rather Julia Lawall
2008-12-29 16:18 ` [PATCH 10/13] drivers/usb/gadget: use USB API functions rather than constants Julia Lawall
2008-12-29 19:54 ` [PATCH 10/13] drivers/usb/gadget: use USB API functions rather Alan Stern
2008-12-29 19:54 ` [PATCH 10/13] drivers/usb/gadget: use USB API functions rather than constants Alan Stern
2008-12-29 20:22 ` David Brownell
2008-12-29 20:22 ` David Brownell
2008-12-29 20:37 ` [PATCH 10/13] drivers/usb/gadget: use USB API functions rather Julia Lawall
2008-12-29 20:37 ` [PATCH 10/13] drivers/usb/gadget: use USB API functions rather than constants Julia Lawall
2008-12-29 20:49 ` [PATCH 10/13] drivers/usb/gadget: use USB API functions rather John Daiker
2008-12-29 20:49 ` [PATCH 10/13] drivers/usb/gadget: use USB API functions rather than constants John Daiker
2008-12-29 21:01 ` David Brownell
2008-12-29 21:01 ` David Brownell
2008-12-29 21:01 ` [PATCH 10/13] drivers/usb/gadget: use USB API functions rather Alan Stern
2008-12-29 21:01 ` [PATCH 10/13] drivers/usb/gadget: use USB API functions rather than constants Alan Stern
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=200812291014.49779.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=gregkh@suse.de \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.