From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ARM: OMAP: raw read and write endian fix
Date: Wed, 2 Apr 2014 08:31:04 -0700 [thread overview]
Message-ID: <20140402153104.GA12234@atomide.com> (raw)
In-Reply-To: <533BE311.7050900@linaro.org>
* Taras Kondratiuk <taras.kondratiuk@linaro.org> [140402 03:18]:
> On 03/26/2014 12:35 PM, Taras Kondratiuk wrote:
> > On 01/08/2014 02:39 AM, Tony Lindgren wrote:
> >> * 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.
> >
> > Hi Tony,
> >
> > It seems omap-for-v3.14/be didn't get into 3.14-rc8.
> > Is there any issue with them?
>
> This series conflicts now with clock changes which got into 3.14.
> Resolution is trivial - just skip conflicting changes.
> omap2_clk_{real,writel} already uses {readl,writel}_relaxed inside.
> Do I need to push an updated series?
Sorry looks like I forgot to merge this branch. I think my plan
was to wait for the clock changes to get merged first..
So yeah, it's probably best that you repost the series after -rc1
is out so we have the conflicting parts cleared. That way the
changes are tested to work for your BE series :)
Regards,
Tony
prev parent reply other threads:[~2014-04-02 15:31 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
2014-03-26 10:35 ` Taras Kondratiuk
2014-04-02 10:14 ` Taras Kondratiuk
2014-04-02 15:31 ` Tony Lindgren [this message]
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=20140402153104.GA12234@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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).