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.2-rc1
Date: Thu, 09 Jul 2015 15:39:27 -0700 [thread overview]
Message-ID: <7hio9tarc0.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20150709094130.GK10644@atomide.com> (Tony Lindgren's message of "Thu, 9 Jul 2015 02:41:30 -0700")
Tony Lindgren <tony@atomide.com> writes:
> The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
>
> Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.2/fixes-rc1
>
> for you to fetch changes up to ae745302c0a3e2b5b768690f631fc14db44467e7:
>
> Merge branch 'fixes-rc1' into omap-for-v4.2/fixes (2015-07-06 05:33:17 -0700)
>
> ----------------------------------------------------------------
> Minor fixes for omaps against v4.2-rc1. Mostly just minor dts changes
> except for a GPMC fix to not use names for probing devices. Also a
> one liner clean-up to remove unecessary return from a void function.
>
> The summary for the changes being:
>
> - Fix probe for GPMC devices by reoving limitations based on device
> name
>
> - Remove unnecessary return from a void function
>
> - Revert beaglebone RTC sleep fix, we now have a better fix merged
>
> - Add am4372 EMIF node to fix a warning
>
> - Add am57xx-beagle-x15 power supply to fix USB2 if USB1 is disabled
>
> - Disable rfbi for am4372 as it does not have a driver
>
> ----------------------------------------------------------------
Pulled into fixes,
Thanks,
Kevin
prev parent reply other threads:[~2015-07-09 22:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 9:41 [GIT PULL] omap fixes against v4.2-rc1 Tony Lindgren
2015-07-09 22:39 ` 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=7hio9tarc0.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).