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 for v4.3 merge window
Date: Wed, 09 Sep 2015 15:53:50 -0700 [thread overview]
Message-ID: <7h8u8fkxvl.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20150903004113.GX10928@atomide.com> (Tony Lindgren's message of "Wed, 2 Sep 2015 17:41:14 -0700")
Tony Lindgren <tony@atomide.com> writes:
> The following changes since commit 2faf962d90ca4c5ee7ba026b7351b1f74500bcdf:
>
> Merge tag 'armsoc-defconfig' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc (2015-09-01 13:17:43 -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-merge-window
>
> for you to fetch changes up to 21b430d23d233c67e6589ea5054d18392e15a28e:
>
> ARM: omap2plus_defconfig: Enable MUSB DMA support (2015-09-01 13:59:25 -0700)
>
> ----------------------------------------------------------------
> Few omap bug fixes that have come up recently:
>
> - Fix deferred probe with omap_device idling unused devices
>
> - Fix booting if no timer parent can be set
>
> - Fix always true warning for vc register check
>
> And also two minor changes not strictly fixes:
>
> - Add SoC detection for dra752
>
> - Enable omap related MUSB DMA engines as we can now
> build them all in finally
>
> ----------------------------------------------------------------
Queuing this into fixes branch for v4.3-rc2.
Thanks,
Kevin
prev parent reply other threads:[~2015-09-09 22:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 0:41 [GIT PULL] omap fixes for v4.3 merge window Tony Lindgren
2015-09-09 22:53 ` 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=7h8u8fkxvl.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