From: Chris Ball <cjb@laptop.org>
To: "T Krishnamoorthy, Balaji" <balajitk@ti.com>
Cc: Venkatraman S <svenkatr@ti.com>,
linux-mmc@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/3] mmc: omap: driver registration cleanups
Date: Thu, 17 May 2012 08:27:24 -0400 [thread overview]
Message-ID: <871umj56xf.fsf@laptop.org> (raw)
In-Reply-To: <CANrkHUaajRTd3D3QU7pfTRN5cv9QaqYcryOs4YNSYHq-kBkYVw@mail.gmail.com> (T. Krishnamoorthy's message of "Thu, 10 May 2012 20:24:37 +0530")
Hi,
On Thu, May 10 2012, T Krishnamoorthy, Balaji wrote:
> On Tue, May 8, 2012 at 5:05 PM, Venkatraman S <svenkatr@ti.com> wrote:
>> Cleanups for the legacy omap mmc driver to remove clutter and
>> make it well behaved as module.
>>
>> Venkatraman S (3):
>> mmc: omap: convert to per instance workqueue
>> mmc: omap: make it behave well as module
>> mmc: omap: convert to module_platform_driver
>
> Looks good to me, So
> Acked-by: Balaji T K <balajitk@ti.com>
Thanks, pushed to mmc-next for 3.5.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-05-17 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 11:35 [PATCH 0/3] mmc: omap: driver registration cleanups Venkatraman S
2012-05-08 11:35 ` [PATCH 1/3] mmc: omap: convert to per instance workqueue Venkatraman S
2012-05-08 11:35 ` [PATCH 2/3] mmc: omap: make it behave well as module Venkatraman S
2012-05-08 11:35 ` [PATCH 3/3] mmc: omap: convert to module_platform_driver Venkatraman S
2012-05-10 14:54 ` [PATCH 0/3] mmc: omap: driver registration cleanups T Krishnamoorthy, Balaji
2012-05-17 12:27 ` Chris Ball [this message]
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=871umj56xf.fsf@laptop.org \
--to=cjb@laptop.org \
--cc=balajitk@ti.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=svenkatr@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox