From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Tony Lindgren <tony@atomide.com>,
arm@kernel.org, linux-omap@vger.kernel.org
Subject: Re: [GIT PULL] late omap mailbox clean-up, driver parts
Date: Tue, 29 Jul 2014 17:36:46 +0200 [thread overview]
Message-ID: <1420246.WMlB29KVsm@wuerfel> (raw)
In-Reply-To: <20140729113917.GP29045@atomide.com>
On Tuesday 29 July 2014 04:39:18 Tony Lindgren wrote:
> The following changes since commit cbf14f3ab9bd6295b345fc812f08ddd844fb183e:
>
> ARM: AM33xx: hwmod_data: Remove legacy mailbox addrs (2014-07-15 05:08:56 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.17/mailbox-cleanup
>
> for you to fetch changes up to 72c1c8179cdc5ba7208d375bd3f104659fc50ad0:
>
> mailbox/omap: add a parent structure for every IP instance (2014-07-29 01:57:25 -0700)
>
> ----------------------------------------------------------------
> Driver specific omap mailbox cleanup. Mostly to remove
> broken legacy code for omap1 and move things towards
> device tree.
>
> These patches were posted a while back, but I did not
> realize I was supposed to merge the driver related
> parts too. So apologies for a late pull request on
> these changes.
Ok, I see. I've merged them into next/drivers now, after first merging in the
first half of the series that we have in the next/soc branch.
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] late omap mailbox clean-up, driver parts
Date: Tue, 29 Jul 2014 17:36:46 +0200 [thread overview]
Message-ID: <1420246.WMlB29KVsm@wuerfel> (raw)
In-Reply-To: <20140729113917.GP29045@atomide.com>
On Tuesday 29 July 2014 04:39:18 Tony Lindgren wrote:
> The following changes since commit cbf14f3ab9bd6295b345fc812f08ddd844fb183e:
>
> ARM: AM33xx: hwmod_data: Remove legacy mailbox addrs (2014-07-15 05:08:56 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.17/mailbox-cleanup
>
> for you to fetch changes up to 72c1c8179cdc5ba7208d375bd3f104659fc50ad0:
>
> mailbox/omap: add a parent structure for every IP instance (2014-07-29 01:57:25 -0700)
>
> ----------------------------------------------------------------
> Driver specific omap mailbox cleanup. Mostly to remove
> broken legacy code for omap1 and move things towards
> device tree.
>
> These patches were posted a while back, but I did not
> realize I was supposed to merge the driver related
> parts too. So apologies for a late pull request on
> these changes.
Ok, I see. I've merged them into next/drivers now, after first merging in the
first half of the series that we have in the next/soc branch.
Arnd
next prev parent reply other threads:[~2014-07-29 15:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 11:39 [GIT PULL] late omap mailbox clean-up, driver parts Tony Lindgren
2014-07-29 11:39 ` Tony Lindgren
2014-07-29 15:36 ` Arnd Bergmann [this message]
2014-07-29 15:36 ` 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=1420246.WMlB29KVsm@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.