From: Chris Ball <cjb@laptop.org>
To: "S, Venkatraman" <svenkatr@ti.com>
Cc: Kevin Hilman <khilman@ti.com>, Juergen Kilb <J.Kilb@phytec.de>,
linux-mmc@vger.kernel.org,
Girish K S <girish.shivananjappa@linaro.org>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH] omap_hsmmc: fix missing parenthesis in pr_info
Date: Thu, 03 Nov 2011 06:42:13 -0400 [thread overview]
Message-ID: <m2sjm58p2y.fsf@bob.laptop.org> (raw)
In-Reply-To: <CANfBPZ8JBJg5QtUcuiDJiORAQkpn6aHvQHddzXO=Qmdo8S1MYw@mail.gmail.com> (Venkatraman S.'s message of "Thu, 3 Nov 2011 13:40:46 +0530")
Hi,
On Thu, Nov 03 2011, S, Venkatraman wrote:
>>> Oops. Thank you; I've pushed this to mmc-next now, and will send the
>>> fix to Linus. I've checked for other errors in the original patch.
>>
>> Where did you push this fix?
>>
>> I don't see this in the mmc-next branch of git://dev.laptop.org/users/cjb/mmc
>>
> MMC tree is back to kernel.org
> http://git.kernel.org/?p=linux/kernel/git/cjb/mmc.git;a=summary
I've deleted the dev.laptop.org mmc tree now, so that there's a clue
that it's moved back to kernel.org. (linux-next is already back to
pulling the kernel.org tree.)
Thanks,
- 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:[~2011-11-03 10:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 19:39 [PATCH] omap_hsmmc: fix missing parenthesis in pr_info Juergen Kilb
2011-10-29 20:04 ` Chris Ball
2011-11-02 23:59 ` Kevin Hilman
2011-11-03 8:10 ` S, Venkatraman
2011-11-03 10:42 ` 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=m2sjm58p2y.fsf@bob.laptop.org \
--to=cjb@laptop.org \
--cc=J.Kilb@phytec.de \
--cc=girish.shivananjappa@linaro.org \
--cc=khilman@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