From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: unlisted-recipients:; Paul Mundt <lethal@linux-sh.org>,
linux-sh@vger.kernel.org, linux-usb@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-mips@linux-mips.org
Subject: Re: [PATCH 5/7] USB: r8a66597-hcd: restore big-endian operation.
Date: Sat, 10 Mar 2012 15:02:38 +0400 [thread overview]
Message-ID: <4F5B34CE.5040900@mvista.com> (raw)
In-Reply-To: <1331311133-26937-5-git-send-email-thomas@codesourcery.com>
Hello.
On 09-03-2012 20:38, Thomas Schwinge wrote:
> On SH, as of 37b7a97884ba64bf7d403351ac2a9476ab4f1bba we have to use the
Please also specify the summary of thta commit in parens.
> endianess-agnostic I/O accessor functions.
> This driver is also enabled in ARM's viper_defconfig as well as MIPS'
> bcm47xx_defconfig and fuloong2e_defconfig -- I suppose none of these are
> operating in big-endian mode, or this issue should already have been noticed
> before.
> The device is now recognized correctly for both litte-endian and big-endian
> sh7785lcr, but I have not tested this any further, as the board is situated in
> a remote data center.
> Signed-off-by: Thomas Schwinge<thomas@codesourcery.com>
> Cc: Paul Mundt<lethal@linux-sh.org>
> Cc: linux-sh@vger.kernel.org
> Cc: linux-usb@vger.kernel.org
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: linux-mips@linux-mips.org
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: Paul Mundt <lethal@linux-sh.org>,
linux-sh@vger.kernel.org, linux-usb@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-mips@linux-mips.org
Subject: Re: [PATCH 5/7] USB: r8a66597-hcd: restore big-endian operation.
Date: Sat, 10 Mar 2012 15:02:38 +0400 [thread overview]
Message-ID: <4F5B34CE.5040900@mvista.com> (raw)
Message-ID: <20120310110238.xY-a3SkOVPK-weRsgUA4e7H4qcegpxbe7WO5m79fICw@z> (raw)
In-Reply-To: <1331311133-26937-5-git-send-email-thomas@codesourcery.com>
Hello.
On 09-03-2012 20:38, Thomas Schwinge wrote:
> On SH, as of 37b7a97884ba64bf7d403351ac2a9476ab4f1bba we have to use the
Please also specify the summary of thta commit in parens.
> endianess-agnostic I/O accessor functions.
> This driver is also enabled in ARM's viper_defconfig as well as MIPS'
> bcm47xx_defconfig and fuloong2e_defconfig -- I suppose none of these are
> operating in big-endian mode, or this issue should already have been noticed
> before.
> The device is now recognized correctly for both litte-endian and big-endian
> sh7785lcr, but I have not tested this any further, as the board is situated in
> a remote data center.
> Signed-off-by: Thomas Schwinge<thomas@codesourcery.com>
> Cc: Paul Mundt<lethal@linux-sh.org>
> Cc: linux-sh@vger.kernel.org
> Cc: linux-usb@vger.kernel.org
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: linux-mips@linux-mips.org
WBR, Sergei
next prev parent reply other threads:[~2012-03-10 11:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1331311133-26937-1-git-send-email-thomas@codesourcery.com>
2012-03-09 16:38 ` [PATCH 5/7] USB: r8a66597-hcd: restore big-endian operation Thomas Schwinge
2012-03-09 16:38 ` Thomas Schwinge
2012-03-10 11:02 ` Sergei Shtylyov [this message]
2012-03-10 11:02 ` Sergei Shtylyov
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=4F5B34CE.5040900@mvista.com \
--to=sshtylyov@mvista.com \
--cc=thomas@codesourcery.com \
/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