From: Brian Norris <computersforpeace@gmail.com>
To: Bean Huo <beanhuo@outlook.com>
Cc: "christian.riesch@omicron.at" <christian.riesch@omicron.at>,
"paul.gortmaker@windriver.com" <paul.gortmaker@windriver.com>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Stijn Devriendt <highguy@gmail.com>
Subject: Re: [PATCH v3] mtd:nor:timeout:fix do_write_buffer() timeout error
Date: Tue, 15 Jul 2014 00:28:23 -0700 [thread overview]
Message-ID: <20140715072823.GH23883@brian-ubuntu> (raw)
In-Reply-To: <BLU185-W7188DFB38D0DD264DF6255A6F60@phx.gbl>
Hi Bean,
On Tue, Jul 15, 2014 at 04:23:44AM +0000, Bean Huo wrote:
> Thanks for your warmly response about my patch.I have been waiting for your message too long.
> It's hard for me to give you a good reason that some flash's CFI parameter is non-zero,and
> incorrect.I just found that if flash'buffer is 512 bytes,not 256 bytes,timeout error will happen.
> If using CFI's timemout value,that is OK.But for cfi_cmdset_0001.c,it also use timeout value of CFI.
> The difference with mine is that if timeout value is not defined in the CFI,the default maxmum timeout
> value is 500000us.
I understand the points here. But this is just a timeout value, so it
isn't a big issue if it's a little too large; but it's a major problem if
it's too short. Since this is an aged driver, which has to accomodate
all sorts of potentially broken chips, I think a "minimum timeout" is a
good idea. And using the current timeout of 2ms (or larger) is fine. So
in pseudocode:
if (CFI_time_typ != 0 && CFI_time_max != 0)
timeout_max = CFI_time_typ + CFI_time_max;
else
timeout_max = 0;
timeout_max = max(timeout_max, 2000);
> Because my company's mailbox title exsits chinese words,and i sent this patch for
> many times,you don't have one response,so i thought that you maybe couldn't receive my email.later,i
> chose my personal email.
It is reasonable to worry about bounced mail occasionally. If the
mailing list rejected your mail, you should get an automated message.
You can also check the archives soon after sending, to make sure your
mail shows up:
http://lists.infradead.org/pipermail/linux-mtd/
And for LKML email, you can check one of several archives mirrors, like
lkml.org.
> For this patch,i will do some changes,please every maintainer and commit-signer check.
Yes, please send a new version (version 4 now?). But please double check
your patch submission, so that it applies correctly this time.
Thanks,
Brian
next prev parent reply other threads:[~2014-07-15 7:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 1:00 [PATCH v3] mtd:nor:timeout:fix do_write_buffer() timeout error bean huo
[not found] ` <CAOY=C6HaXPrEGPSzEUb5XM79SdqTSGwMPmQXq3U7abNvW0SuQA@mail.gmail.com>
[not found] ` <BLU185-W959F702F780985563AD7C0A60E0@phx.gbl>
[not found] ` <CAOY=C6GcNzvBieUVm1pk4XQipxj3U9N1Dw09JEM6ZdW7jJLjcA@mail.gmail.com>
[not found] ` <BLU185-W92FA6A378C0039524F045FA60E0@phx.gbl>
[not found] ` <CAOY=C6FG8fgZGKhXvXG03hQQNSOYz+=uqrfYmNXfHKkz4XRSog@mail.gmail.com>
[not found] ` <BLU185-W73A028C46FBD1D13672BC0A6090@phx.gbl>
2014-07-12 6:46 ` Brian Norris
2014-07-15 4:23 ` Bean Huo
2014-07-15 7:28 ` Brian Norris [this message]
2014-07-16 6:22 ` Bean Huo
-- strict thread matches above, loose matches on Subject: below --
2014-07-09 0:43 Bean Huo
2014-07-07 6:05 Bean Huo 霍斌斌 (beanhuo)
2014-07-03 0:40 Bean Huo 霍斌斌 (beanhuo)
2014-06-30 7:56 Bean Huo 霍斌斌 (beanhuo)
2014-07-12 6:30 ` Brian Norris
2014-07-12 6:37 ` Brian Norris
2014-06-24 17:03 Bean Huo 霍斌斌 (beanhuo)
2014-06-24 2:02 Bean Huo 霍斌斌 (beanhuo)
2014-06-24 6:17 ` Christian Riesch
2014-06-24 6:21 ` Bean Huo 霍斌斌 (beanhuo)
2014-06-24 6:59 ` Christian Riesch
2014-06-24 6:55 ` Christian Riesch
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=20140715072823.GH23883@brian-ubuntu \
--to=computersforpeace@gmail.com \
--cc=beanhuo@outlook.com \
--cc=christian.riesch@omicron.at \
--cc=dwmw2@infradead.org \
--cc=highguy@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=paul.gortmaker@windriver.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