From: Chris Ball <chris@printf.net>
To: Balaji T K <balajitk@TI.COM>
Cc: linux-mmc@vger.kernel.org, Daniel Mack <zonque@gmail.com>,
tony@atomide.com, linux-omap@vger.kernel.org
Subject: Re: [PATCH RESEND] mmc: omap_hsmmc: support more DT properties
Date: Tue, 04 Mar 2014 17:39:28 +0000 [thread overview]
Message-ID: <86ob1lrhgv.fsf@void.printf.net> (raw)
In-Reply-To: <5315FD28.4020800@ti.com> (Balaji T. K.'s message of "Tue, 4 Mar 2014 21:49:52 +0530")
Hi Balaji,
On Tue, Mar 04 2014, Balaji T K wrote:
> git://git.ti.com/~balajitk/ti-linux-kernel/omap-hsmmc.git omap_hsmmc-for-3.15
Thanks, all pushed to mmc-next for 3.15.
- Chris.
--
Chris Ball <chris@printf.net> <http://printf.net/>
prev parent reply other threads:[~2014-03-04 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 21:16 [PATCH RESEND] mmc: omap_hsmmc: support more DT properties Daniel Mack
2014-03-04 16:19 ` Balaji T K
2014-03-04 17:37 ` Tony Lindgren
2014-03-04 17:39 ` 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=86ob1lrhgv.fsf@void.printf.net \
--to=chris@printf.net \
--cc=balajitk@TI.COM \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
--cc=zonque@gmail.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;
as well as URLs for NNTP newsgroup(s).