From: Chris Ball <cjb@laptop.org>
To: Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>
Cc: "'Philip Rakity'" <prakity@marvell.com>,
"'Kyungmin Park'" <kmpark@infradead.org>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
andrew.chih.howe.khor@intel.com, kok.howg.ewe@intel.com,
Toshiharu Okada <toshiharu-linux@dsn.okisemi.com>
Subject: Re: A MMC card transfer issue
Date: Wed, 19 Jan 2011 01:41:26 +0000 [thread overview]
Message-ID: <20110119014126.GA21707@void.printf.net> (raw)
In-Reply-To: <A564AB9DDD054732981B672320B7C9B0@hacdom.okisemi.com>
On Wed, Jan 19, 2011 at 10:29:21AM +0900, Tomoya MORINAGA wrote:
> On Wednesday, January 19, 2011 10:00 AM, Philip Rakity wrote:
> > I just looked in the 2.6.37 code and the fix is not there.
> > It is in the 2.6.37 linus tree.
> >
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.g
> > it;a=blob;f=drivers/mmc/core/mmc.c;h=16006ef153fe081c2f0f0a09c
> > d4443ce7f3c49a1;hb=a25cecce88194b2edf38b8c3b1665e9318eb2d22
>
> Do you know when the above patch will be integrated to kernel ?
I don't understand, sorry. The link is to a file, not a patch, and
Philip's statement above talks about a patch being in 2.6.37 but not
being in 2.6.37, which I don't understand either.
Looking back farther in the thread, I think you're both talking about:
http://git.kernel.org/?p=linux/kernel/git/cjb/mmc.git;a=commit;h=15ec44611904be0dcc97b84c29fbf964e5e2b36f
This patch was merged into Linus' 2.6.37-rc4 on Nov 27 2010, and
released as part of 2.6.37.
Can you elaborate on your question, if it's still outstanding?
Thanks,
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-01-19 1:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 5:39 A MMC card transfer issue Tomoya MORINAGA
2010-11-09 5:53 ` Kyungmin Park
2010-11-09 7:29 ` Tomoya MORINAGA
2010-11-11 2:59 ` Tomoya MORINAGA
2010-12-01 1:08 ` Tomoya MORINAGA
[not found] ` <2D50F985-2383-4406-8514-DFE462A5F546@marvell.com>
[not found] ` <4D2E0464ABB54FFF9C10583336E27879@hacdom.okisemi.com>
2011-01-19 0:59 ` Philip Rakity
2011-01-19 1:29 ` Tomoya MORINAGA
2011-01-19 1:41 ` Chris Ball [this message]
2011-01-19 3:12 ` Philip Rakity
2011-01-19 6:05 ` Philip Rakity
2011-01-19 6:30 ` Tomoya MORINAGA
2011-01-19 17:42 ` Chris Ball
2011-01-19 23:49 ` Tomoya MORINAGA
2011-01-26 8:28 ` Tomoya MORINAGA
2011-01-26 15:42 ` Philip Rakity
2011-01-27 1:00 ` Tomoya MORINAGA
2011-01-27 1:03 ` Philip Rakity
2011-01-27 1:31 ` Tomoya MORINAGA
2011-01-27 1:43 ` Philip Rakity
2011-01-27 3:20 ` Tomoya MORINAGA
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=20110119014126.GA21707@void.printf.net \
--to=cjb@laptop.org \
--cc=andrew.chih.howe.khor@intel.com \
--cc=kmpark@infradead.org \
--cc=kok.howg.ewe@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=prakity@marvell.com \
--cc=tomoya-linux@dsn.okisemi.com \
--cc=toshiharu-linux@dsn.okisemi.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