[Top] [All Lists]

RE: [PATCH v2 1/2] usb: chipidea: big-endian support

To: Svetoslav Neykov <>, 'Ralf Baechle' <>, 'Greg Kroah-Hartman' <>, 'Gabor Juhos' <>, 'John Crispin' <>, 'Alan Stern' <>, "'Luis R. Rodriguez'" <>
Subject: RE: [PATCH v2 1/2] usb: chipidea: big-endian support
From: Alexander Shishkin <>
Date: Fri, 29 Mar 2013 17:09:50 +0200
In-reply-to: <023c01ce2c03$1886e220$4994a660$>
List-archive: <>
List-help: <>
List-id: linux-mips <>
List-owner: <>
List-post: <>
List-software: Ecartis version 1.0.0
List-subscribe: <>
List-unsubscribe: <>
References: <> <> <> <023c01ce2c03$1886e220$4994a660$>
User-agent: Notmuch/0.12+187~ga2502b0 ( Emacs/23.4.1 (x86_64-pc-linux-gnu)
Svetoslav Neykov <> writes:

> Alexander Shishkin wrote:
>> Svetoslav Neykov <> writes:
>>> Convert between big-endian and little-endian format when accessing the
> usb controller structures which are little-endian by specification.
>>> Fix cases where the little-endian memory layout is taken for granted.
>>> The patch doesn't have any effect on the already supported
>>> little-endian architectures.
>>Applied to my branch of things that are aiming at v3.10. Next time
>>please make sure that it applies cleanly.
> I am a bit confused about the workflow and which repository to base my work
> on. Should I use github/virtuoso/linux-ci for my future patches? Or
> linux-next?

It really depends on what your patches change. For chipidea driver
changes, yes it's that branch. For mips-related bits, it's most probably
something else. For gadget, otg or phy patches, it's Felipe's tree. If
you get it wrong, normally it shouldn't be too much work to rebase your
patches onto a different tree, especially for the author of the
patches. In some cases I might do it for you, but you should be aware of
possible penalties [1]. :)

For the coming merge window I'm fixing and rebasing everything for
everybody anyway, so this time it's no big deal.



<Prev in Thread] Current Thread [Next in Thread>