From: Olof Johansson <olof@lixom.net>
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 soc clean-up for v4.4 merge window
Date: Mon, 26 Oct 2015 14:36:59 +0900 [thread overview]
Message-ID: <20151026053659.GC4216@localhost> (raw)
In-Reply-To: <20151024204209.GB892@atomide.com>
On Sat, Oct 24, 2015 at 01:42:10PM -0700, Tony Lindgren wrote:
> The following changes since commit 049e6dde7e57f0054fdc49102e7ef4830c698b46:
>
> Linux 4.3-rc4 (2015-10-04 16:57:17 +0100)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.4/soc-clean-up
>
> for you to fetch changes up to ef4da0c1c8f3ca3e9dcf6936bf687a32cd62f293:
>
> Merge tag 'for-v4.4/omap-hwmod-cleanup-a' of git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending into omap-for-v4.4/soc (2015-10-23 18:13:38 -0700)
>
> ----------------------------------------------------------------
> Minimal omap SoC changes for v4.4 merge window. As we've spent quite a
> bit of time sorting out regressions for v4.3 and are very late with
> these, I've kept the changes down to minimum:
>
> - A series of timer changes from Felipe Balbi to get us closer to
> moving the remaining timer code into drivers
>
> - A series of hwmod clean-up changes queued by Paul Walmsley
>
> - SoC detection clean-up to use soc_is instead of cpu_is as CPU is
> within the SoC and is confusing naming. The rest we can now change
> along with the other clean-up
This is arriving a bit late, but I've merged it anyway since it's cleanup.
Hopefully we won't see much regressions from it during the -rc cycle.
-Olof
prev parent reply other threads:[~2015-10-26 5:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-24 20:42 [GIT PULL] omap soc clean-up for v4.4 merge window Tony Lindgren
2015-10-26 5:36 ` Olof Johansson [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=20151026053659.GC4216@localhost \
--to=olof@lixom.net \
--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).