From: Brian Norris <computersforpeace@gmail.com>
To: "Bean Huo 霍斌斌 (beanhuo)" <beanhuo@micron.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jingoo Han <jg1.han@samsung.com>,
Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
"b32955@freescale.com" <b32955@freescale.com>,
Christian Riesch <christian.riesch@omicron.at>
Subject: Re: [PATCH v3] mtd:nor:timeout:fix do_write_buffer() timeout error
Date: Fri, 11 Jul 2014 23:37:49 -0700 [thread overview]
Message-ID: <20140712063749.GC23883@brian-ubuntu> (raw)
In-Reply-To: <20140712063041.GB23883@brian-ubuntu>
On Fri, Jul 11, 2014 at 11:30:41PM -0700, Brian Norris wrote:
> I see that you have sent this several times in a relatively short
> period, and I see that there are several comments you haven't addressed
> [1] [2].
Wow, and I just noticed there are 3 more recent copies of this patch,
with as few as 2 days' wait in between! Please back off from that. You
can remind by replying to the original email. If you really think
everyone has forgetten your patch (after much more than just a week), a
resend may be worth it.
Brian
next prev parent reply other threads:[~2014-07-12 6:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 7:56 [PATCH v3] mtd:nor:timeout:fix do_write_buffer() timeout error Bean Huo 霍斌斌 (beanhuo)
2014-07-12 6:30 ` Brian Norris
2014-07-12 6:37 ` Brian Norris [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-09 1:00 bean huo
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-24 17:03 Bean Huo 霍斌斌 (beanhuo)
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=20140712063749.GC23883@brian-ubuntu \
--to=computersforpeace@gmail.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=b32955@freescale.com \
--cc=beanhuo@micron.com \
--cc=christian.riesch@omicron.at \
--cc=dwmw2@infradead.org \
--cc=jg1.han@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).