linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, arm@kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 1/2] omap fixes for v4.7 merge window
Date: Fri, 3 Jun 2016 12:28:53 -0700	[thread overview]
Message-ID: <20160603192853.GJ3761@localhost> (raw)
In-Reply-To: <57360add.8803430a.9585b.ffffa6d9SMTPIN_ADDED_BROKEN@mx.google.com>

On Fri, May 13, 2016 at 10:11:40AM -0700, Tony Lindgren wrote:
> The following changes since commit 7472931f7f1e9d91f761dce30107ae345b61a5c3:
> 
>   ARM: dts: omap5: fix range of permitted wakeup pinmux registers (2016-04-26 10:16:12 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.7/fixes-v2
> 
> for you to fetch changes up to 65db875d110b8e517f81fa71c57a65fc6d0019ac:
> 
>   ARM: OMAP2+: AM43XX: Enable fixes for Cortex-A9 errata (2016-05-12 13:47:51 -0700)
> 
> ----------------------------------------------------------------
> Two fixes for omaps for v4.7 merge window, one to enable
> ARM errata for am437x, and the other to add ARM errtum
> workaround for dra7.
> 
> AFAIK these both can wait for v4.7, we can then request them
> for stable kernels as needed.

Merged to fixes.


-Olof

       reply	other threads:[~2016-06-03 19:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <57360add.8803430a.9585b.ffffa6d9SMTPIN_ADDED_BROKEN@mx.google.com>
2016-06-03 19:28 ` Olof Johansson [this message]
2016-05-13 17:11 [GIT PULL 1/2] omap fixes for v4.7 merge window 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=20160603192853.GJ3761@localhost \
    --to=olof@lixom.net \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).