From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] OMAP: omap_device cleanup for v3.2
Date: Wed, 21 Sep 2011 11:20:51 -0700 [thread overview]
Message-ID: <20110921182051.GH2937@atomide.com> (raw)
In-Reply-To: <87y5xps6kv.fsf@ti.com>
* 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?
Tony
> [1]
> commit 456f69c544d4298e921dc0c606492cdbaa60b34b
> Author: Kevin Hilman <khilman@deeprootsystems.com>
> Date: Tue Sep 6 21:04:10 2011 +0100
>
> ARM: 7082/1: platform_device: pdev_archdata: add omap_device pointer
>
> Add omap_device pointer to the ARM-specific arch data in the
> platform_device. This will be used to attach OMAP-specific
> device-data to the platform device with device lifetime.
>
> Suggested-by: Russell King <rmk+kernel@arm.linux.org.uk>
>
> Acked-by: Grant Likely <grant.likely@secretlab.ca>
> Signed-off-by: Kevin Hilman <khilman@ti.com>
> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-09-21 18:20 UTC|newest]
Thread overview: 5+ 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:56 ` Kevin Hilman
2011-09-21 18:20 ` Tony Lindgren [this message]
2011-09-21 18:39 ` 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=20110921182051.GH2937@atomide.com \
--to=tony@atomide.com \
--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