From: Fan Du <fan.du@windriver.com>
To: David Miller <davem@davemloft.net>
Cc: <herbert@gondor.hengli.com.au>, <netdev@vger.kernel.org>
Subject: Re: [PATCH] [XFRM] Fix unexpected SA hard expiration after changing date
Date: Thu, 2 Aug 2012 16:58:24 +0800 [thread overview]
Message-ID: <501A4130.9000004@windriver.com> (raw)
In-Reply-To: <20120802.002308.367808111426941908.davem@davemloft.net>
Hi, all
*Apologize* for all the trouble I brought to everyone, who gave me
advices/suggestions using fdu@windriver.com.
I'm truly sorry that all the inconvenience caused by my mistake.
fdu@windriver.com is obsolete!!!
I will use fan.du@windriver.com from now on.
Thanks
On 2012年08月02日 15:23, David Miller wrote:
>
> You know what Fan Du, I'm extremely irritated about your email
> situation.
>
> Every time you post a patch, I reply, and I get this crap:
>
> Diagnostic-Code: smtp; 5.1.0 - Unknown address error 550-'5.2.1<fdu@windriver.com>... Mailbox disabled for this recipient' (delivery attempts: 0)
>
> I've seen this at least 7 times, and this absolutely has to stop.
>
> Otherwise I'm ignoring every patch you submit, it's as simple as
> that.
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Love each day!
--fan
next prev parent reply other threads:[~2012-08-02 8:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 7:43 [XFRM][PATCH v5] Fix unexpected SA hard expiration after setting new date Fan Du
2012-07-31 7:43 ` [PATCH] [XFRM] Fix unexpected SA hard expiration after changing date Fan Du
2012-08-02 7:21 ` David Miller
2012-08-02 7:23 ` David Miller
2012-08-02 7:23 ` David Miller
2012-08-02 8:58 ` Fan Du [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-27 2:39 [RESEND][XFRM][PATCH v4] Fix unexpected SA hard expiration after setting new date Fan Du
2012-07-27 2:39 ` [PATCH] [XFRM] Fix unexpected SA hard expiration after changing date Fan Du
2012-07-30 6:15 ` David Miller
2012-06-21 6:26 [XFRM][RFC v4] Fix unexpected SA hard expiration after setting new date Fan Du
2012-06-21 6:26 ` [PATCH] [XFRM] Fix unexpected SA hard expiration after changing date Fan Du
2012-06-25 22:29 ` David Miller
2012-06-19 9:28 [XFRM][RFC v3] Fix unexpected SA hard expiration after setting new date Fan Du
2012-06-19 9:28 ` [PATCH] [XFRM] Fix unexpected SA hard expiration after changing date Fan Du
2012-06-19 7:51 [XFRM][RFC v2] Fix unexpected SA hard expiration after setting new date fan.du
2012-06-19 7:51 ` [PATCH] [XFRM] Fix unexpected SA hard expiration after changing date fan.du
2012-06-19 9:01 ` David Miller
2012-06-19 9:05 ` David Miller
2012-06-21 2:11 ` Fan Du
2012-06-21 3:43 ` David Miller
2012-06-21 6:41 ` Fan Du
2012-06-21 4:06 ` David Miller
2012-06-18 8:24 [XFRM][RFC v1] Fix unexpected SA hard expiration after setting new date fan.du
2012-06-18 8:24 ` [PATCH] [XFRM] Fix unexpected SA hard expiration after changing date fan.du
2012-06-18 11:05 ` Steffen Klassert
2012-06-19 1:34 ` Fan Du
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=501A4130.9000004@windriver.com \
--to=fan.du@windriver.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.hengli.com.au \
--cc=netdev@vger.kernel.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).