From: Arnd Bergmann <arnd@arndb.de>
To: Tony Lindgren <tony@atomide.com>
Cc: arm@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-omap@vger.kernel.org
Subject: Re: [GIT PULL] omap soc changes for v3.17 merge window
Date: Sat, 26 Jul 2014 11:35:11 +0200 [thread overview]
Message-ID: <5148043.QCGen0hlse@wuerfel> (raw)
In-Reply-To: <20140724115850.GC29045@atomide.com>
On Thursday 24 July 2014 04:58:50 Tony Lindgren wrote:
> SoC related changes for omaps for v3.17 merge window:
>
> - Add device tree and hwmod data for various devices
> for new SoCs
>
> - Remove legacy mailbox hwmod data that's no longer
> needed for SoCs that are DT only. Note that this may
> cause a minor merge conflict in mach-omap2/devices.c
> with omap_init_mbox() and omap_init_hdmi_audio(), both
> are legacy code that is getting removed
Very good, merged into next/soc. Thanks,
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap soc changes for v3.17 merge window
Date: Sat, 26 Jul 2014 11:35:11 +0200 [thread overview]
Message-ID: <5148043.QCGen0hlse@wuerfel> (raw)
In-Reply-To: <20140724115850.GC29045@atomide.com>
On Thursday 24 July 2014 04:58:50 Tony Lindgren wrote:
> SoC related changes for omaps for v3.17 merge window:
>
> - Add device tree and hwmod data for various devices
> for new SoCs
>
> - Remove legacy mailbox hwmod data that's no longer
> needed for SoCs that are DT only. Note that this may
> cause a minor merge conflict in mach-omap2/devices.c
> with omap_init_mbox() and omap_init_hdmi_audio(), both
> are legacy code that is getting removed
Very good, merged into next/soc. Thanks,
Arnd
next prev parent reply other threads:[~2014-07-26 9:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 11:58 [GIT PULL] omap soc changes for v3.17 merge window Tony Lindgren
2014-07-24 11:58 ` Tony Lindgren
2014-07-26 9:35 ` Arnd Bergmann [this message]
2014-07-26 9:35 ` Arnd Bergmann
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=5148043.QCGen0hlse@wuerfel \
--to=arnd@arndb.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.