From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: David Brownell <david-b@pacbell.net>
Cc: Julia Lawall <julia@diku.dk>,
gregkh@suse.de, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] include/linux: Move definitions from usb.h to usb/ch9.h
Date: Fri, 02 Jan 2009 02:01:48 +0000 [thread overview]
Message-ID: <20090102020121.GA9411@gamba.jf.intel.com> (raw)
In-Reply-To: <200812301740.26432.david-b@pacbell.net>
On Tue, Dec 30, 2008 at 05:40:26PM -0800, David Brownell wrote:
> On Tuesday 30 December 2008, Sarah Sharp wrote:
> > so why move these functions to
> > include/linux/usb/ch9.h? Was it confusing to find these functions, or do you
> > have an overall plan for these changes?
>
> You missed earlier mail on the topic. The basic issue is
> that those symbols can (and should!) be used for peripheral
> side support as well as host side support ... which means
> they should never have been put into a host-only header.
Ah, I see. Thanks for the explanation. :)
Sarah
--
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: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: David Brownell <david-b@pacbell.net>
Cc: Julia Lawall <julia@diku.dk>,
gregkh@suse.de, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] include/linux: Move definitions from usb.h to usb/ch9.h
Date: Thu, 1 Jan 2009 18:01:48 -0800 [thread overview]
Message-ID: <20090102020121.GA9411@gamba.jf.intel.com> (raw)
In-Reply-To: <200812301740.26432.david-b@pacbell.net>
On Tue, Dec 30, 2008 at 05:40:26PM -0800, David Brownell wrote:
> On Tuesday 30 December 2008, Sarah Sharp wrote:
> > so why move these functions to
> > include/linux/usb/ch9.h? Was it confusing to find these functions, or do you
> > have an overall plan for these changes?
>
> You missed earlier mail on the topic. The basic issue is
> that those symbols can (and should!) be used for peripheral
> side support as well as host side support ... which means
> they should never have been put into a host-only header.
Ah, I see. Thanks for the explanation. :)
Sarah
next prev parent reply other threads:[~2009-01-02 2:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 21:48 [PATCH] include/linux: Move definitions from usb.h to usb/ch9.h Julia Lawall
2008-12-29 21:48 ` Julia Lawall
2008-12-30 0:25 ` David Brownell
2008-12-30 0:25 ` David Brownell
2008-12-30 23:39 ` Sarah Sharp
2008-12-30 23:39 ` Sarah Sharp
2008-12-31 1:40 ` David Brownell
2008-12-31 1:40 ` David Brownell
2009-01-02 2:01 ` Sarah Sharp [this message]
2009-01-02 2:01 ` Sarah Sharp
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=20090102020121.GA9411@gamba.jf.intel.com \
--to=sarah.a.sharp@linux.intel.com \
--cc=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 \
/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.