From: "Subhash Jadavani" <subhashj@codeaurora.org>
To: 'Chris Ball' <cjb@laptop.org>
Cc: linux-mmc@vger.kernel.org, linux-arm-msm@vger.kernel.org,
'Namjae Jeon' <linkinjeon@gmail.com>
Subject: RE: [PATCH v1 1/1] mmc: block: replace __blk_end_request() with blk_end_request()
Date: Thu, 7 Jun 2012 15:50:55 +0530 [thread overview]
Message-ID: <000501cd4497$3b31ead0$b195c070$@codeaurora.org> (raw)
In-Reply-To: <87mx4g4lft.fsf@octavius.laptop.org>
> -----Original Message-----
> From: Chris Ball [mailto:cjb@laptop.org]
> Sent: Wednesday, June 06, 2012 7:01 PM
> To: Subhash Jadavani
> Cc: linux-mmc@vger.kernel.org; linux-arm-msm@vger.kernel.org; 'Namjae
> Jeon'
> Subject: Re: [PATCH v1 1/1] mmc: block: replace __blk_end_request() with
> blk_end_request()
>
> Hi,
>
> On Sat, May 19 2012, Subhash Jadavani wrote:
> > Do you see any issues with this patch?
>
> No, no issues -- please could I ask you to refresh it against 3.5-rc1 (it
no longer
> applies) and add your performance numbers to the commit message? I'll
push
> it to mmc-next and probably merge for 3.6, so that we have a full round of
> linux-next for anyone to notice problems.
Thanks Chris. I have posted v2 of this patch against mmc-next tip.
Regards,
Subhash
>
> Thanks!
>
> - Chris.
> --
> Chris Ball <cjb@laptop.org> <http://printf.net/>
> One Laptop Per Child
prev parent reply other threads:[~2012-06-07 10:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 18:26 [PATCH v1 1/1] mmc: block: replace __blk_end_request() with blk_end_request() Subhash Jadavani
2012-04-10 18:38 ` Chris Ball
2012-04-10 18:51 ` Subhash Jadavani
2012-04-18 5:15 ` Subhash Jadavani
2012-04-18 5:42 ` Namjae Jeon
2012-04-18 7:36 ` Subhash Jadavani
2012-05-19 11:04 ` Subhash Jadavani
2012-06-06 13:30 ` Chris Ball
2012-06-07 10:20 ` Subhash Jadavani [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='000501cd4497$3b31ead0$b195c070$@codeaurora.org' \
--to=subhashj@codeaurora.org \
--cc=cjb@laptop.org \
--cc=linkinjeon@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
/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).