All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Benoit Cousson <b-cousson@ti.com>
Cc: paul@pwsan.com, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/6] OMAP: omap_device cleanup before device-tree integration
Date: Tue, 27 Sep 2011 14:32:32 -0700	[thread overview]
Message-ID: <87pqily8lr.fsf@ti.com> (raw)
In-Reply-To: <1317143886-13285-1-git-send-email-b-cousson@ti.com> (Benoit Cousson's message of "Tue, 27 Sep 2011 19:18:00 +0200")

Benoit Cousson <b-cousson@ti.com> writes:

> Hi Kevin,
>
> Here are a couple of cleanups on top of your for_3.2/omap_device branch.
>
> patches are available here:
> git://gitorious.org/omap-pm/linux.git for_3.2/1_omap_device_cleanup

Thanks, this series looks good now.  Queuing for v3.2 here:

   git://github.com/khilman/linux-omap-pm.git for_3.2/omap_device-2

Kevin

WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/6] OMAP: omap_device cleanup before device-tree integration
Date: Tue, 27 Sep 2011 14:32:32 -0700	[thread overview]
Message-ID: <87pqily8lr.fsf@ti.com> (raw)
In-Reply-To: <1317143886-13285-1-git-send-email-b-cousson@ti.com> (Benoit Cousson's message of "Tue, 27 Sep 2011 19:18:00 +0200")

Benoit Cousson <b-cousson@ti.com> writes:

> Hi Kevin,
>
> Here are a couple of cleanups on top of your for_3.2/omap_device branch.
>
> patches are available here:
> git://gitorious.org/omap-pm/linux.git for_3.2/1_omap_device_cleanup

Thanks, this series looks good now.  Queuing for v3.2 here:

   git://github.com/khilman/linux-omap-pm.git for_3.2/omap_device-2

Kevin

  parent reply	other threads:[~2011-09-27 21:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-27 17:18 [PATCH v3 0/6] OMAP: omap_device cleanup before device-tree integration Benoit Cousson
2011-09-27 17:18 ` Benoit Cousson
2011-09-27 17:18 ` [PATCH v3 1/6] OMAP: omap_device: Add omap_device_get_by_hwmod_name Benoit Cousson
2011-09-27 17:18   ` Benoit Cousson
2011-09-27 17:18 ` [PATCH v3 2/6] OMAP3: beagle-board: Use the omap_hwmod_name_get_dev API Benoit Cousson
2011-09-27 17:18   ` Benoit Cousson
2011-09-27 17:18 ` [PATCH v3 3/6] OMAP2+: pm: Use hwmod name instead of dev pointer Benoit Cousson
2011-09-27 17:18   ` Benoit Cousson
2011-09-27 17:18 ` [PATCH v3 4/6] OMAP2+: pm: Remove static devices variable for mpu, dsp, iva and l3 PM Benoit Cousson
2011-09-27 17:18   ` Benoit Cousson
2011-09-27 17:18 ` [PATCH v3 5/6] OMAP: omap_device: Create a default omap_device_pm_latency Benoit Cousson
2011-09-27 17:18   ` Benoit Cousson
2011-09-27 17:30   ` Tony Lindgren
2011-09-27 17:30     ` Tony Lindgren
2011-09-27 18:29     ` Kevin Hilman
2011-09-27 18:29       ` Kevin Hilman
2011-09-27 18:37       ` Tony Lindgren
2011-09-27 18:37         ` Tony Lindgren
2011-09-27 17:18 ` [PATCH v3 6/6] OMAP2+: devices: Remove all omap_device_pm_latency structures Benoit Cousson
2011-09-27 17:18   ` Benoit Cousson
2011-09-27 21:32 ` Kevin Hilman [this message]
2011-09-27 21:32   ` [PATCH v3 0/6] OMAP: omap_device cleanup before device-tree integration 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=87pqily8lr.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=b-cousson@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.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.