From: Kevin Hilman <khilman@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Russell King <rmk@arm.linux.org.uk>
Subject: Re: [GIT PULL] OMAP: omap_device cleanup for v3.2
Date: Wed, 21 Sep 2011 11:39:22 -0700 [thread overview]
Message-ID: <87ty853fl1.fsf@ti.com> (raw)
In-Reply-To: <20110921182051.GH2937@atomide.com> (Tony Lindgren's message of "Wed, 21 Sep 2011 11:20:51 -0700")
Tony Lindgren <tony@atomide.com> writes:
> * Kevin Hilman <khilman@ti.com> [110915 16:23]:
>> Kevin Hilman <khilman@ti.com> writes:
>>
>> > Please pull this omap_device cleanup series for v3.2. This sets the
>> > groundwork for Benoit's DT infrastructure work.
>>
>> Turns out this series has a dependency on a patch[1] in Russell's
>> for-next branch.
>>
>> Russell, any chance of picking this patch into your devel-stable so we
>> have a fixed point to merge with?
>
> Or maybe Kevin can add it to his series instead?
Sure.
Russell, if you're OK with dropping it from your for-next, I'll just
add it to my series where the dependencies are.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] OMAP: omap_device cleanup for v3.2
Date: Wed, 21 Sep 2011 11:39:22 -0700 [thread overview]
Message-ID: <87ty853fl1.fsf@ti.com> (raw)
In-Reply-To: <20110921182051.GH2937@atomide.com> (Tony Lindgren's message of "Wed, 21 Sep 2011 11:20:51 -0700")
Tony Lindgren <tony@atomide.com> writes:
> * Kevin Hilman <khilman@ti.com> [110915 16:23]:
>> Kevin Hilman <khilman@ti.com> writes:
>>
>> > Please pull this omap_device cleanup series for v3.2. This sets the
>> > groundwork for Benoit's DT infrastructure work.
>>
>> Turns out this series has a dependency on a patch[1] in Russell's
>> for-next branch.
>>
>> Russell, any chance of picking this patch into your devel-stable so we
>> have a fixed point to merge with?
>
> Or maybe Kevin can add it to his series instead?
Sure.
Russell, if you're OK with dropping it from your for-next, I'll just
add it to my series where the dependencies are.
Kevin
next prev parent reply other threads:[~2011-09-21 18:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 23:38 [GIT PULL] OMAP: omap_device cleanup for v3.2 Kevin Hilman
2011-09-15 23:38 ` Kevin Hilman
2011-09-15 23:56 ` Kevin Hilman
2011-09-15 23:56 ` Kevin Hilman
2011-09-21 18:20 ` Tony Lindgren
2011-09-21 18:20 ` Tony Lindgren
2011-09-21 18:39 ` Kevin Hilman [this message]
2011-09-21 18:39 ` Kevin Hilman
2011-09-22 16:33 ` Kevin Hilman
2011-09-22 16:33 ` Kevin Hilman
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=87ty853fl1.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--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.