From: Tony Lindgren <tony@atomide.com>
To: Taras Kondratiuk <taras.kondratiuk@linaro.org>
Cc: Patch Tracking <patches@linaro.org>,
Linaro Networking <linaro-networking@linaro.org>,
Linaro Kernel <linaro-kernel@lists.linaro.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] ARM: OMAP: raw read and write endian fix
Date: Tue, 7 Jan 2014 16:39:28 -0800 [thread overview]
Message-ID: <20140108003927.GJ5074@atomide.com> (raw)
In-Reply-To: <CAArO44vC4WKGHSqHX3+Mo5+jcNuyJLkh94+SPd4H+aZYAroYzw@mail.gmail.com>
* Taras Kondratiuk <taras.kondratiuk@linaro.org> [131223 10:20]:
> On 23 December 2013 20:10, Taras Kondratiuk <taras.kondratiuk@linaro.org> wrote:
> > This series does trivial replacement of __raw_xxx functions with xxx_relaxed
> > endian-neutral variants in 'mach-omap2' and 'plat-omap' directories.
> > Some code here most probably won't be used in BE mode (like debug-leds for
> > OMAP1 boards), but changes are made anyway to remove __raw_xxx() functions
> > completely and simplify future grep'ing for new __raw_xxx() entries.
Sorry for the delay on these, applying into omap-for-v3.14/be.
These are trivial, and it's actually nice that you left out the
assembly related changes as those should be acked by the PM
people in case there are some issues dealing with the ROM code
etc.
Regards,
Tony
next prev parent reply other threads:[~2014-01-08 0:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1387822234-11167-1-git-send-email-taras.kondratiuk@linaro.org>
2013-12-23 18:10 ` [PATCH 1/4] ARM: OMAP2+: raw read and write endian fix Taras Kondratiuk
2013-12-23 18:10 ` [PATCH 2/4] ARM: OMAP: dmtimer: " Taras Kondratiuk
2013-12-23 18:10 ` [PATCH 3/4] ARM: OMAP: counter-32k: " Taras Kondratiuk
2013-12-23 18:10 ` [PATCH 4/4] ARM: OMAP: debug-leds: " Taras Kondratiuk
2013-12-23 18:18 ` [PATCH 0/4] ARM: OMAP: " Taras Kondratiuk
2014-01-08 0:39 ` Tony Lindgren [this message]
2014-03-26 10:35 ` Taras Kondratiuk
2014-04-02 10:14 ` Taras Kondratiuk
2014-04-02 15:31 ` Tony Lindgren
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=20140108003927.GJ5074@atomide.com \
--to=tony@atomide.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linaro-networking@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=patches@linaro.org \
--cc=taras.kondratiuk@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).