From: Brian Norris <computersforpeace@gmail.com>
To: Bean Huo <beanhuo@outlook.com>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
Jingoo Han <jg1.han@samsung.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"christian.riesch@omicron.at" <christian.riesch@omicron.at>,
Huang Shijie <b32955@freescale.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH v6] mtd:nor:timeout:fix do_write_buffer() timeout error
Date: Wed, 16 Jul 2014 18:17:24 -0700 [thread overview]
Message-ID: <20140717011724.GW7537@ld-irv-0074> (raw)
In-Reply-To: <BLU185-W53748517956B27745D7033A6F40@phx.gbl>
On Thu, Jul 17, 2014 at 12:54:17AM +0000, Bean Huo wrote:
> > I have just fixed up your patch myself, to use max() and to improve some
> > of the language. Let me know if the below works for you.
>
> hi,Brian
> Thanks once again.I test and it works Ok.It can be accepted now?
Yes. Pushed to l2-mtd.git.
Please be more diligent next time to follow CodingStyle and email
submission practices next time. Even if your company email gives
trouble, I'm sure you can find some way to send patches properly. For
instance, a quick search shows me that your outlook.com email supports
sending email via SMTP:
http://windows.microsoft.com/en-us/windows/outlook/send-receive-from-app
That means you can, for instance, use git-send-email to send patches.
Brian
next prev parent reply other threads:[~2014-07-17 1:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 16:05 [PATCH v6] mtd:nor:timeout:fix do_write_buffer() timeout error Bean Huo
2014-07-16 18:04 ` Brian Norris
2014-07-17 0:54 ` Bean Huo
2014-07-17 1:17 ` Brian Norris [this message]
2014-07-23 11:39 ` Gupta, Pekon
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=20140717011724.GW7537@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=b32955@freescale.com \
--cc=beanhuo@outlook.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