From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: JJ Ding <jj_ding@emc.com.tw>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
"Seth Forshee" <seth.forshee@canonical.com>,
"Aaron Huang" <aaron_huang@emc.com.tw>,
"Tom Lin" <tom_lin@emc.com.tw>,
"Éric Piel" <E.A.B.Piel@tudelft.nl>,
"Daniel Kurtz" <djkurtz@chromium.org>,
"Chase Douglas" <chase.douglas@canonical.com>,
"Henrik Rydberg" <rydberg@euromail.se>,
"Alessandro Rubini" <rubini@cvml.unipv.it>
Subject: Re: [PATCH v2 0/7] Input: elantech: add support for newer hardware
Date: Tue, 23 Aug 2011 23:10:51 -0700 [thread overview]
Message-ID: <20110824061051.GA15604@core.coreip.homeip.net> (raw)
In-Reply-To: <87wre31hnu.fsf@emc.com.tw>
Hi JJ,
On Wed, Aug 24, 2011 at 01:51:17PM +0800, JJ Ding wrote:
> Sorry.
> linux-kernel and linux-input complains patch #2's subject
> ETP_2FT_XXXX looks like spam.
> (5.1.0 - Unknown address error 550-'5.7.1 Content-Policy reject msg: The
> capital Triple-X in subject is way too often associated with junk email,
> please rephrase. BF:<H 0>; S1752956Ab1HXFgV'
> )
> so patch #2 is blocked.
> Please ignore this series.
> I will rephase and resend.
Just resend that one patch changing subject to ETP_2FT_* or similar...
No need to resend the rest of the patches.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2011-08-24 6:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 5:38 [PATCH v2 0/7] Input: elantech: add support for newer hardware JJ Ding
2011-08-24 5:38 ` [PATCH v2 1/7] Input: elantech - correct x, y value range for v2 hardware JJ Ding
2011-08-24 5:38 ` [PATCH v2 3/7] Input: elantech - use firmware provided x, y ranges JJ Ding
2011-08-24 5:38 ` [PATCH v2 4/7] Input: elantech - remove ETP_EDGE_FUZZ_V2 JJ Ding
2011-08-24 5:38 ` [PATCH v2 5/7] Input: elantech - packet checking for v2 hardware JJ Ding
2011-08-24 5:38 ` [PATCH v2 6/7] Input: elantech - clean up elantech_init JJ Ding
2011-08-24 5:38 ` [PATCH v2 7/7] Input: elantech - add v3 hardware support JJ Ding
2011-08-24 5:51 ` [PATCH v2 0/7] Input: elantech: add support for newer hardware JJ Ding
2011-08-24 6:10 ` Dmitry Torokhov [this message]
2011-08-24 6:29 ` [PATCH v2 2/7] Input: elantech - get rid of ETP_2FT_* in elantech.h JJ Ding
2011-08-24 7:56 ` [PATCH v2 0/7] Input: elantech: add support for newer hardware Daniel Kurtz
-- strict thread matches above, loose matches on Subject: below --
2011-08-24 5:44 JJ Ding
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=20110824061051.GA15604@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=E.A.B.Piel@tudelft.nl \
--cc=aaron_huang@emc.com.tw \
--cc=chase.douglas@canonical.com \
--cc=djkurtz@chromium.org \
--cc=jj_ding@emc.com.tw \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rubini@cvml.unipv.it \
--cc=rydberg@euromail.se \
--cc=seth.forshee@canonical.com \
--cc=tom_lin@emc.com.tw \
/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).