From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, aramoto@linux-ipv6.org,
kozakai@linux-ipv6.org, yoshfuji@linux-ipv6.org,
nhorman@tuxdriver.com
Subject: Re: [GIT PULL] IPv6 Updates
Date: Wed, 21 Feb 2007 17:03:04 +0900 (JST) [thread overview]
Message-ID: <20070221.170304.65080002.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <20070220.231545.104035801.davem@davemloft.net>
In article <20070220.231545.104035801.davem@davemloft.net> (at Tue, 20 Feb 2007 23:15:45 -0800 (PST)), David Miller <davem@davemloft.net> says:
> From: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
> Date: Thu, 15 Feb 2007 02:35:14 +0900 (JST)
>
> > Please consider pulling the following changesets available on the
> > 2.6.20-net-2.6-20070214-FOR_DAVEM
> > branch at
> > <git://git.linux-ipv6.org/gitroot/yoshfuji/linux-2.6-dev.git>
> > (on top of commit 928ba4169dc1d82c83105831f5ddb5472379b440).
>
> Unfortunately, the merge window is closed so I really cannot merge all
> of this, only bug fixes at this point.
>
> If you would like to avoid this, please be more prompt in merging to
> me next time the merge window opens up.
Sorry about that.
The ipv4-in-ipv6 functionality depends on the cross-protocol ipsec
framework, which was not ready earlier, so I hesitated.
Anyway, I'll cook up 2 trees; one for fix and another for 2.6.22.
I'll send a note when the "fix" tree has become ready.
And, I will queue the Optimistic DAD patch as well other changes into
my "dev" tree.
Regards,
--yoshfuji
next prev parent reply other threads:[~2007-02-21 8:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 17:35 [GIT PULL] IPv6 Updates YOSHIFUJI Hideaki / 吉藤英明
2007-02-14 19:12 ` Vlad Yasevich
2007-02-14 19:19 ` Hasso Tepper
2007-02-14 20:57 ` Herbert Xu
2007-02-14 21:31 ` Herbert Xu
2007-02-14 22:38 ` Hugo Santos
2007-02-21 8:06 ` David Miller
2007-02-21 8:09 ` YOSHIFUJI Hideaki / 吉藤英明
2007-02-21 7:15 ` David Miller
2007-02-21 8:03 ` YOSHIFUJI Hideaki / 吉藤英明 [this message]
2007-02-21 9:29 ` David Miller
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=20070221.170304.65080002.yoshfuji@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=aramoto@linux-ipv6.org \
--cc=davem@davemloft.net \
--cc=kozakai@linux-ipv6.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.