From: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Richard Weinberger <richard@nod.at>, <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH] ubi: do not re-read the data already read out in retry
Date: Tue, 25 Aug 2015 08:34:22 +0800 [thread overview]
Message-ID: <55DBB80E.9080100@cn.fujitsu.com> (raw)
In-Reply-To: <20150824165916.GG81844@google.com>
On 08/25/2015 12:59 AM, Brian Norris wrote:
> On Mon, Aug 24, 2015 at 03:04:02PM +0800, Dongsheng Yang wrote:
>> TBH, my customer send me this requirement and I cooked this patch
>> to them.
>
> Ah, so it's highly likely the driver is just terrible! In that case, I'd
> suggest a nice NAK, until we find a legitimate use case.
Agreed, thanx Brian.
Yang
>
> Regards,
> Brian
>
next prev parent reply other threads:[~2015-08-25 0:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 7:59 [PATCH] ubi: do not re-read the data already read out in retry Dongsheng Yang
2015-08-21 9:17 ` Richard Weinberger
2015-08-24 1:05 ` Dongsheng Yang
2015-08-24 6:46 ` Richard Weinberger
2015-08-24 7:04 ` Dongsheng Yang
2015-08-24 16:59 ` Brian Norris
2015-08-25 0:34 ` Dongsheng Yang [this message]
2015-08-24 16:50 ` Brian Norris
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=55DBB80E.9080100@cn.fujitsu.com \
--to=yangds.fnst@cn.fujitsu.com \
--cc=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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).