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] few minor omap fixes against v4.4-rc6
Date: Tue, 22 Dec 2015 13:24:51 -0800	[thread overview]
Message-ID: <20151222212451.GG30172@localhost> (raw)
In-Reply-To: <20151221205418.GD2793@atomide.com>

On Mon, Dec 21, 2015 at 12:54:19PM -0800, Tony Lindgren wrote:
> The following changes since commit 14054fb1da099fd89208b8b319a00e0b902c7645:
> 
>   ARM: dts: am4372: fix clock source for arm twd and global timers (2015-12-09 16:46:25 -0800)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.4/fixes-rc6
> 
> for you to fetch changes up to 0b4d6972d7b052b23d33ff9bdbb52958664fbb26:
> 
>   ARM: dts: Fix UART wakeirq for omap4 duovero parlor (2015-12-18 16:43:22 -0800)
> 
> ----------------------------------------------------------------
> Few fixes for omaps to allow am437x only builds to boot properly with
> CPU_IDLE and ARM TWD timer. This is probably a common configuration setup
> for people making products with these SoCs so let's make sure it works.
> 
> Also a wakeirq fix for duovero parlor making my life a bit easier as that
> allows me to run basic PM regression tests on it.
> 
> It would be nice to have these in v4.4, but if it gets too late for that
> because of the holidays, it is not super critical if these get merged for
> v4.5.
> 

Merged into fixes for v4.4.


Thanks,

-Olof

      reply	other threads:[~2015-12-22 21:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-21 20:54 [GIT PULL] few minor omap fixes against v4.4-rc6 Tony Lindgren
2015-12-22 21:24 ` Olof Johansson [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=20151222212451.GG30172@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).