From: Johannes Berg <johannes@sipsolutions.net>
To: Greg Ungerer <gerg@uclinux.org>, netdev@vger.kernel.org
Cc: Lucas Stach <l.stach@pengutronix.de>,
Fugang Duan <B38611@freescale.com>, Arnd Bergmann <arnd@arndb.de>,
Shawn Guo <shawnguo@kernel.org>
Subject: Re: [PATCH v2] net: fec: make driver endian-safe
Date: Mon, 25 Jan 2016 08:53:36 +0100 [thread overview]
Message-ID: <1453708416.2164.0.camel@sipsolutions.net> (raw)
In-Reply-To: <56A571C1.5050905@uclinux.org>
On Mon, 2016-01-25 at 10:52 +1000, Greg Ungerer wrote:
>
> I tested this on a ColdFire (5208) target that uses this driver.
> Simple testing showed it working with no problems. The ColdFire
> SoC processors use a version of the FEC hardware module, and they
> always run big-endian.
>
Great, thanks!
FWIW, I failed to mention this - I did test the new version also on
little-endian ARM.
johannes
next prev parent reply other threads:[~2016-01-25 7:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-24 15:52 [PATCH v2] net: fec: make driver endian-safe Johannes Berg
2016-01-24 16:49 ` Arnd Bergmann
2016-01-24 19:12 ` Johannes Berg
2016-01-25 0:52 ` Greg Ungerer
2016-01-25 7:53 ` Johannes Berg [this message]
2016-01-25 18:52 ` David Miller
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=1453708416.2164.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=B38611@freescale.com \
--cc=arnd@arndb.de \
--cc=gerg@uclinux.org \
--cc=l.stach@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=shawnguo@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.