linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/4] trivial omap big endian changes for v3.14 merge window
Date: Tue, 14 Jan 2014 14:33:27 -0800	[thread overview]
Message-ID: <20140114223326.GD18512@atomide.com> (raw)
In-Reply-To: <871u0a6vqf.fsf@linaro.org>

* Kevin Hilman <khilman@linaro.org> [140114 14:33]:
> Tony Lindgren <tony@atomide.com> writes:
> 
> > The following changes since commit 413541dd66d51f791a0b169d9b9014e4f56be13c:
> >
> >   Linux 3.13-rc5 (2013-12-22 13:08:32 -0800)
> >
> > are available in the git repository at:
> >
> >   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.14/be-signed
> >
> > for you to fetch changes up to fc6ca98c81bf0ea8b46064915b5947b971594101:
> >
> >   ARM: OMAP: debug-leds: raw read and write endian fix (2014-01-07 16:09:45 -0800)
> >
> > ----------------------------------------------------------------
> > Trivial search and replace of read and write functions to allow
> > further patches to make omaps work also in big endian mode.
> >
> > ----------------------------------------------------------------
> 
> I think this one should wait for v3.15.  While a trivial rename, it's a
> pretty broad change and risks having conflicts and fallouts with other
> changes (thinking especially of ongoing clock changes.)

Sure no problem.

Tony

  reply	other threads:[~2014-01-14 22:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09  1:19 [GIT PULL 1/4] non-urgent omap fixes for v3.14 merge window Tony Lindgren
2014-01-09  1:20 ` [GIT PULL 2/4] omap device tree " Tony Lindgren
2014-01-14 22:30   ` Kevin Hilman
2014-01-09  1:21 ` [GIT PULL 3/4] trivial omap big endian changes " Tony Lindgren
2014-01-14 22:31   ` Kevin Hilman
2014-01-14 22:33     ` Tony Lindgren [this message]
2014-01-09  1:22 ` [GIT PULL 4/4] GIC crossbar support " Tony Lindgren
2014-01-14 22:40   ` Kevin Hilman

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=20140114223326.GD18512@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).