From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/2] omap non-urgent fixes for v3.20, part 2
Date: Mon, 26 Jan 2015 20:29:01 -0800 [thread overview]
Message-ID: <20150127042901.GJ22154@quad.lixom.net> (raw)
In-Reply-To: <54c6ad8d.8182440a.13ff.15c1SMTPIN_ADDED_BROKEN@mx.google.com>
On Mon, Jan 26, 2015 at 01:08:18PM -0800, Tony Lindgren wrote:
> The following changes since commit 13efcb188984f69e1f97b4d9e7d3663fb782946f:
>
> ARM: OMAP2+: Disable omap3 PM init for ti81xx (2015-01-14 17:37:16 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.20/fixes-not-urgent-pt2
>
> for you to fetch changes up to 20d9448a59770420ead8078fb76948de32765fe6:
>
> Merge tag 'for-v3.20/omap-hwmod-a' of git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending into omap-for-v3.20/fixes-not-urgent (2015-01-21 16:52:17 -0800)
>
> ----------------------------------------------------------------
> Non-critical fixes for omap hwmod code via Paul Walmsley <paul@pwsan.com>:
>
> 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/
Merged, thanks.
-Olof
next parent reply other threads:[~2015-01-27 4:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54c6ad8d.8182440a.13ff.15c1SMTPIN_ADDED_BROKEN@mx.google.com>
2015-01-27 4:29 ` Olof Johansson [this message]
2015-01-26 21:08 [GIT PULL 1/2] omap non-urgent fixes for v3.20, part 2 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=20150127042901.GJ22154@quad.lixom.net \
--to=olof@lixom.net \
--cc=linux-arm-kernel@lists.infradead.org \
/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