From: David Miller <davem@davemloft.net>
To: shinta@sfc.wide.ad.jp
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 0/5] [XFRM,PFKEYV2]: MIGRATE support (take 2)
Date: Wed, 07 Feb 2007 16:52:13 -0800 (PST) [thread overview]
Message-ID: <20070207.165213.98418769.davem@davemloft.net> (raw)
In-Reply-To: <20070208093935.90CA.SHINTA@sfc.wide.ad.jp>
From: Shinta Sugimoto <shinta@sfc.wide.ad.jp>
Date: Thu, 08 Feb 2007 09:42:00 +0900
> I noticed that I sent wrong version (not the newest one) of the
> patch set by mistake. I will re-post the patch set soon, so could
> you please wait for that? I am sorry for the confusion.
Ok, no problem.
next prev parent reply other threads:[~2007-02-08 0:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 0:42 Fw: [PATCH 0/5] [XFRM,PFKEYV2]: MIGRATE support (take 2) Shinta Sugimoto
2007-02-08 0:52 ` David Miller [this message]
2007-02-08 21:32 ` [PATCH 0/5] NET Improve layering of structs dst_entry/rtable/rt6_info/dn_route to get less dcache footprint Eric Dumazet
2007-02-10 1:31 ` David Miller
2007-02-10 8:17 ` Eric Dumazet
2007-02-08 21:33 ` [PATCH 1/5] NET : Introduce union in struct dst_entry to hold 'next' pointer Eric Dumazet
-- strict thread matches above, loose matches on Subject: below --
2007-02-07 13:17 [PATCH 0/5] [XFRM,PFKEYV2]: MIGRATE support (take 2) Shinta Sugimoto
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=20070207.165213.98418769.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shinta@sfc.wide.ad.jp \
/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).