On Tue, Apr 02, 2013 at 07:07:36PM +0100, David Howells wrote:
> Sarah Sharp wrote:
>
> > I guess my question is a deeper one: do we need to rename all the xHCI
> > macros to have the XHCI_ prefix, in order to avoid future collision?
> > For example, one of the macros is MAX_HC_PORTS, which
Sarah Sharp wrote:
> I guess my question is a deeper one: do we need to rename all the xHCI
> macros to have the XHCI_ prefix, in order to avoid future collision?
> For example, one of the macros is MAX_HC_PORTS, which could possibly be
> used by other host drivers in the future.
Hmmm...
I
Sarah Sharp sarah.a.sh...@linux.intel.com wrote:
I guess my question is a deeper one: do we need to rename all the xHCI
macros to have the XHCI_ prefix, in order to avoid future collision?
For example, one of the macros is MAX_HC_PORTS, which could possibly be
used by other host drivers in
On Tue, Apr 02, 2013 at 07:07:36PM +0100, David Howells wrote:
Sarah Sharp sarah.a.sh...@linux.intel.com wrote:
I guess my question is a deeper one: do we need to rename all the xHCI
macros to have the XHCI_ prefix, in order to avoid future collision?
For example, one of the macros is
On Thu, Mar 28, 2013 at 10:32:53PM +, David Howells wrote:
> Sarah Sharp wrote:
>
> > I'm a little bit confused about your description for the second one.
> > Did you need to change the #defines names because they could conflict
> > with other drivers when the xHCI driver is built in? Or is
Sarah Sharp wrote:
> I'm a little bit confused about your description for the second one.
> Did you need to change the #defines names because they could conflict
> with other drivers when the xHCI driver is built in? Or is there some
> other point I'm missing?
Sorry, I should say. I'm trying
Hi Dave,
I'm a little bit confused about your description for the second one.
Did you need to change the #defines names because they could conflict
with other drivers when the xHCI driver is built in? Or is there some
other point I'm missing?
Are these feature patches for 3.10, or bug fixes for
Rename SEGMENT_SIZE and SEGMENT_SHIFT as the former is used in a.out.h.
Signed-off-by: David Howells
cc: Sarah Sharp
cc: Greg Kroah-Hartman
cc: linux-...@vger.kernel.org
---
drivers/usb/host/xhci-mem.c | 16
drivers/usb/host/xhci.h |4 ++--
2 files changed, 10
Rename SEGMENT_SIZE and SEGMENT_SHIFT as the former is used in a.out.h.
Signed-off-by: David Howells dhowe...@redhat.com
cc: Sarah Sharp sarah.a.sh...@linux.intel.com
cc: Greg Kroah-Hartman gre...@linuxfoundation.org
cc: linux-...@vger.kernel.org
---
drivers/usb/host/xhci-mem.c | 16
Hi Dave,
I'm a little bit confused about your description for the second one.
Did you need to change the #defines names because they could conflict
with other drivers when the xHCI driver is built in? Or is there some
other point I'm missing?
Are these feature patches for 3.10, or bug fixes for
Sarah Sharp sarah.a.sh...@linux.intel.com wrote:
I'm a little bit confused about your description for the second one.
Did you need to change the #defines names because they could conflict
with other drivers when the xHCI driver is built in? Or is there some
other point I'm missing?
Sorry, I
On Thu, Mar 28, 2013 at 10:32:53PM +, David Howells wrote:
Sarah Sharp sarah.a.sh...@linux.intel.com wrote:
I'm a little bit confused about your description for the second one.
Did you need to change the #defines names because they could conflict
with other drivers when the xHCI
12 matches
Mail list logo
