From: Jon Hunter <jonathanh@nvidia.com>
To: Grant Grundler <grundler@google.com>
Cc: Gwendal Grignou <gwendal@chromium.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Seshagiri Holi <sholi@nvidia.com>, Arnd Bergmann <arnd@arndb.de>,
Olof Johansson <olofj@chromium.org>
Subject: Re: [PATCH V3] mmc: block: Add new ioctl to send multi commands
Date: Tue, 22 Sep 2015 10:29:13 +0100 [thread overview]
Message-ID: <56011F69.9080706@nvidia.com> (raw)
In-Reply-To: <CANEJEGtxy=d0mQCJJGg=DFKhAC+cWMe48JL_8U_K+g=_kQ1K3A@mail.gmail.com>
On 21/09/15 19:40, Grant Grundler wrote:
> Jon, Ulf,
> Can we first get the current implementation upstream and _then_ add
> more patches to it?
>
> On Mon, Sep 21, 2015 at 4:19 AM, Jon Hunter <jonathanh@nvidia.com> wrote:
> ...
>>>>> + for (i = 0; i < num_of_cmds; i++) {
>>>>> + err = __mmc_blk_ioctl_cmd(card, md, idata[i]);
>>>>> + if (err) {
>>>>> + mmc_put_card(card);
>>>>> + goto cmd_done;
>>>> Instead of exiting here, you should first copy to the user the data
>>>> and response of successful commands, mark the failed command as failed
>>>> and the remaining ones as "not executed".
>>>> This way, it will be easier for the user space application to find out
>>>> where the sequence failed. This especially true if some reverts are
>>>> needed.
>>>
>>> Yes that sounds like a sensible thing to do. I will incorporate that change.
>
> I also liked Gwendal's idea and incorporated that into our 3.18 kernel
> tree here:
> https://chromium-review.googlesource.com/#/c/299956
>
> (this is on top of Jon's most recently proposed patch - we'll align
> with what lands shortly)
>
> But as I've demonstrated, this can be a separate patch.
Yes that's fine with me. I have just posted a V4 to address Ulf's last
comment.
Cheers
Jon
prev parent reply other threads:[~2015-09-22 9:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 15:00 [PATCH V3] mmc: block: Add new ioctl to send multi commands Jon Hunter
2015-09-14 16:36 ` Grant Grundler
2015-09-16 11:08 ` Ulf Hansson
2015-09-16 16:01 ` Jon Hunter
2015-09-17 6:59 ` Ulf Hansson
2015-09-18 10:24 ` Jon Hunter
2015-09-16 17:54 ` Gwendal Grignou
2015-09-21 9:56 ` Jon Hunter
2015-09-21 11:19 ` Jon Hunter
2015-09-21 18:40 ` Grant Grundler
2015-09-22 9:29 ` Jon Hunter [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=56011F69.9080706@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=arnd@arndb.de \
--cc=grundler@google.com \
--cc=gwendal@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=olofj@chromium.org \
--cc=sholi@nvidia.com \
--cc=ulf.hansson@linaro.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).