From: John Crispin <blogic@openwrt.org>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: "Gabor Juhos" <juhosg@openwrt.org>,
=?gb18030?Q?=C0=EE=C3=CF=CE=B0?= <emong@vip.qq.com>,
"David Woodhouse" <dwmw2@infradead.org>,
linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: =?gb18030?Q?=BB=D8=B8=B4=A3=BA_=5BPATCH=5D_mtd=3A_m25p80=3A_add_support_for_the_EON_EN25Q64_chip?=
Date: Wed, 29 Aug 2012 13:26:24 +0200 [thread overview]
Message-ID: <503DFC60.8050209@openwrt.org> (raw)
In-Reply-To: <tencent_6D2D2DEF7090853310893273@qq.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 210 bytes --]
On 29/08/12 13:20, ÀîÃÏΰ wrote:
> I tested on my tp-link 4310 with SECT_4K or without SECT_4K.
> both works.
>
>
Hi Artem,
can you drop my patch in favour of the one with SECT_4K in it please.
Thanks,
John
next parent reply other threads:[~2012-08-29 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_6D2D2DEF7090853310893273@qq.com>
2012-08-29 11:26 ` John Crispin [this message]
2012-08-29 12:47 ` 回复: [PATCH] mtd: m25p80: add support for the EON EN25Q64 chip Artem Bityutskiy
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=503DFC60.8050209@openwrt.org \
--to=blogic@openwrt.org \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=emong@vip.qq.com \
--cc=juhosg@openwrt.org \
--cc=linux-mtd@lists.infradead.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).