From: Andrey Borzenkov <arvidjaar@gmail.com>
To: Brian Haley <brian.haley@hp.com>
Cc: "David Miller" <davem@davemloft.net>,
"Vladislav Yasevich" <vladislav.yasevich@hp.com>,
"Chuck Lever" <chuck.lever@oracle.com>,
"Theodore Tso" <tytso@mit.edu>,
Valdis.Kletnieks@vt.edu, "Rafael J. Wysocki" <rjw@sisk.pl>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
bonding-devel@lists.sourceforge.net,
"J.A. Magallón" <jamagallon@ono.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Jay Vosburgh" <fubar@us.ibm.com>
Subject: Re: [PATCH 0/2] Bonding: fix IPv6 module requirement regression
Date: Wed, 4 Mar 2009 07:20:30 +0300 [thread overview]
Message-ID: <200903040720.34497.arvidjaar@gmail.com> (raw)
In-Reply-To: <49ADE956.1020702@hp.com>
[-- Attachment #1: Type: text/plain, Size: 688 bytes --]
On 4 марта 2009 05:37:10 Brian Haley wrote:
> These patches fix the Bonding module's requirement to have the IPv6
> module loaded and configured by creating a new "disable" module
> parameter value for ipv6.ko. This allows users who do not want any
> IPv6 addresses or sockets to be created to disable IPv6 support,
> while still loading the module and making it's symbols available.
> This can be specified in /etc/modprobe.conf (or similar) with
> "options ipv6 disable=1".
>
While this is definitely the right approach, it requires completely new
infrastructure to disable IPv6 (including resolving update issues). So I
guess this is post-2.6.29 material.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-03-04 4:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 2:37 [PATCH 0/2] Bonding: fix IPv6 module requirement regression Brian Haley
2009-03-04 4:20 ` Andrey Borzenkov [this message]
2009-03-04 11:11 ` 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=200903040720.34497.arvidjaar@gmail.com \
--to=arvidjaar@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=bonding-devel@lists.sourceforge.net \
--cc=brian.haley@hp.com \
--cc=chuck.lever@oracle.com \
--cc=davem@davemloft.net \
--cc=fubar@us.ibm.com \
--cc=jamagallon@ono.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tytso@mit.edu \
--cc=vladislav.yasevich@hp.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).