From: Kevin Hilman <khilman@kernel.org>
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] omap fixes against v4.3-rc1
Date: Wed, 16 Sep 2015 09:33:14 -0700 [thread overview]
Message-ID: <7hwpvqfho5.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20150915154650.GS10928@atomide.com> (Tony Lindgren's message of "Tue, 15 Sep 2015 08:46:50 -0700")
Tony Lindgren <tony@atomide.com> writes:
> The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
>
> Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.3/fixes-rc1
>
> for you to fetch changes up to 60fdcb8863d9b4a8b6c6b367886fadb50d4c0b07:
>
> ARM: dts: Fixup model name for HP t410 dts (2015-09-14 13:33:47 -0700)
>
> ----------------------------------------------------------------
> Fixes for omaps against v4.3-rc1:
>
> - Fix long time regression on beagle for tfp410 pin muxing
>
> - Fix dm814x control base address typo and related Ethernet
> phy configuration
>
> - Fix igepv2 Ethernet pinmuxing as only some boards have it
>
> - Fix pbias regulator compatible values as a pending regulator
> fix needs those for MMC1 to work properly
>
> - Fix beagle-x15 MMC1 regulator and make pcf857x built-in
>
> - Fix omap5 and dra7 Kconfig options when built as the only
> SoCs selected
>
> - Fix PM errata for omap5 and dra7 as they too need it
>
> - Fix phycore mpu voltage
>
> Also included are a few cosmetic fixes:
>
> - Remove unused of_irq macros
>
> - Fix dra7 ethernet name
>
> ----------------------------------------------------------------
Thanks, pulled into fixes.
Kevin
prev parent reply other threads:[~2015-09-16 16:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 15:46 [GIT PULL] omap fixes against v4.3-rc1 Tony Lindgren
2015-09-15 16:48 ` Tony Lindgren
2015-09-16 16:33 ` Kevin Hilman [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=7hwpvqfho5.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--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).