From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] ARM: OMAP2+: hwmod: first set of patches for v3.20
Date: Wed, 21 Jan 2015 16:54:26 -0800 [thread overview]
Message-ID: <20150122005426.GV7718@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1501212338100.5450@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [150121 15:42]:
> Hi Tony
>
> The following changes since commit 97bf6af1f928216fd6c5a66e8a57bfa95a659672:
>
> Linux 3.19-rc1 (2014-12-20 17:08:50 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git tags/for-v3.20/omap-hwmod-a
>
> for you to fetch changes up to 1c7e36bfc3e2fb2df5e2d1989a4b6fb9055a0f9b:
>
> ARM: DRA7: hwmod: Fix boot crash with DEBUG_LL enabled on UART3 (2015-01-20 18:12:17 -0700)
>
> ----------------------------------------------------------------
> ARM: OMAP2+: hwmod: first set of patches for v3.20
>
> First set of OMAP2+ hwmod patches for Linux v3.20. These are mostly
> fixes for warnings, although there's one DRA7xx patch that fixes
> CONFIG_DEBUG_LL for AM572x/DRA7xx SoCs that use UART3 for console,
> such as the BeagleBoard-X15.
>
> These patches entered Linux-next starting with the next-20150121 tag.
>
> Basic build, boot, and PM test results can be found here:
>
> http://www.pwsan.com/omap/testlogs/omap-hwmod-a-for-v3.20/20150121142621/
Thanks pulling into omap-for-v3.20/fixes-not-urgent.
Tony
prev parent reply other threads:[~2015-01-22 0:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 23:39 [GIT PULL] ARM: OMAP2+: hwmod: first set of patches for v3.20 Paul Walmsley
2015-01-22 0:54 ` Tony Lindgren [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=20150122005426.GV7718@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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).