From: Chris Ball <cjb@laptop.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-mmc@vger.kernel.org, Magnus Damm <magnus.damm@gmail.com>
Subject: Re: My outstanding MMC / SDHI/TMIO / MMCIF patches for 3.6
Date: Fri, 29 Jun 2012 19:25:21 -0400 [thread overview]
Message-ID: <87lij5aefy.fsf@octavius.laptop.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1206292041340.9152@axis700.grange> (Guennadi Liakhovetski's message of "Fri, 29 Jun 2012 20:44:50 +0200 (CEST)")
Hi Guennadi,
On Fri, Jun 29 2012, Guennadi Liakhovetski wrote:
> Ah, ok, right, sorry, I thought, it would be a part of the "git
> request-pull" output.
It is for newer versions of git, FWIW.
> So, the top commit has hash
>
> 7c4cf5b31b98f51ebfc8db89b022e4f52f93f5db
>
> Hope, this is what's required :-)
Yes, perfect -- pulled and pushed out to mmc-next. Thanks!
Could we get a file in Documentation/devicetree/bindings/mmc/ for the
new sh_mmcif DT bindings you've added, please? It can come as a new
patch on top of these. I know it'll be very short right now; you can
at least show an example of a DT node that works.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2012-06-29 23:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 8:36 My outstanding MMC / SDHI/TMIO / MMCIF patches for 3.6 Guennadi Liakhovetski
2012-06-28 14:29 ` Chris Ball
2012-06-29 15:03 ` Guennadi Liakhovetski
2012-06-29 16:26 ` Chris Ball
2012-06-29 18:44 ` Guennadi Liakhovetski
2012-06-29 23:25 ` Chris Ball [this message]
2012-06-30 10:45 ` Guennadi Liakhovetski
2012-06-30 12:52 ` Chris Ball
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=87lij5aefy.fsf@octavius.laptop.org \
--to=cjb@laptop.org \
--cc=g.liakhovetski@gmx.de \
--cc=linux-mmc@vger.kernel.org \
--cc=magnus.damm@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 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.