Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Tony Lindgren <tony@atomide.com>
Cc: arm@kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-omap@vger.kernel.org
Subject: Re: [GIT PULL] omap fixes against v3.16-rc4
Date: Thu, 10 Jul 2014 14:35:54 -0700	[thread overview]
Message-ID: <20140710213554.GA1313@quad.lixom.net> (raw)
In-Reply-To: <20140709153552.GA28884@atomide.com>

On Wed, Jul 09, 2014 at 08:35:52AM -0700, Tony Lindgren wrote:
> The following changes since commit cd3de83f147601356395b57a8673e9c5ff1e59d1:
> 
>   Linux 3.16-rc4 (2014-07-06 12:37:51 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.16/fixes-rc4
> 
> for you to fetch changes up to 1d29a0722f6c38f79785c9ffb911730598de84e2:
> 
>   ARM: OMAP2+: Remove non working OMAP HDMI audio initialization (2014-07-08 01:08:44 -0700)
> 
> ----------------------------------------------------------------
> Fixes for omaps for the -rc series. It's mostly fixes for clock rates,
> restart handling and phy regulators and SATA interconnect data.

It's a little surprising to see a SATA fix about a week after enablement
went in during -rc -- enabling it that late should ideally have been
better tested than this.

> Also few build fixes related to the DSP driver in staging, and trivial
> stuff like removal of broken and soon to be unused platform data init
> for HDMI audio that would be good to get into the -rc series if not
> too late.

Thanks, merged. Definitely time for regressions only from here on out though.


-Olof

  reply	other threads:[~2014-07-10 21:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09 15:35 [GIT PULL] omap fixes against v3.16-rc4 Tony Lindgren
2014-07-10 21:35 ` Olof Johansson [this message]
2014-07-11  6:30   ` 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=20140710213554.GA1313@quad.lixom.net \
    --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