From: "David S. Miller" <davem@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: netdev@oss.sgi.com
Subject: Re: Initialising net/ipv4/ before net/ipv6/ breaks IPv6 autoconf with nfsroot....
Date: Fri, 20 Feb 2004 11:07:17 -0800 [thread overview]
Message-ID: <20040220110717.4c8e9f59.davem@redhat.com> (raw)
In-Reply-To: <1077303696.427.570.camel@hades.cambridge.redhat.com>
On Fri, 20 Feb 2004 19:01:37 +0000
David Woodhouse <dwmw2@infradead.org> wrote:
> On Thu, 2004-02-19 at 22:22 -0800, David S. Miller wrote:
> > If at some point we create some initialization dependency between ipv4
> > and ipv6 (f.e. ipv6 init needs some ipv4 table setup) we will need to
> > tread carefully to keep this from breaking.
>
> True. For 2.6 in fact we can do it this way...
I like this version of this fix a lot, applied.
next prev parent reply other threads:[~2004-02-20 19:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 14:38 Initialising net/ipv4/ before net/ipv6/ breaks IPv6 autoconf with nfsroot David Woodhouse
2004-02-20 6:22 ` David S. Miller
2004-02-20 19:01 ` David Woodhouse
2004-02-20 19:07 ` David S. Miller [this message]
2004-02-20 19:02 ` David Woodhouse
2004-02-20 19:08 ` David S. 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=20040220110717.4c8e9f59.davem@redhat.com \
--to=davem@redhat.com \
--cc=dwmw2@infradead.org \
--cc=netdev@oss.sgi.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 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).