From: David Miller <davem@davemloft.net>
To: greearb@candelatech.com
Cc: netdev@vger.kernel.org
Subject: Re: [net-next] ipv6: Export in6addr_any for use by modules.
Date: Wed, 01 Sep 2010 11:07:10 -0700 (PDT) [thread overview]
Message-ID: <20100901.110710.67895761.davem@davemloft.net> (raw)
In-Reply-To: <4C7D89CF.3040307@candelatech.com>
From: Ben Greear <greearb@candelatech.com>
Date: Tue, 31 Aug 2010 16:01:35 -0700
> On 08/31/2010 10:08 AM, Ben Greear wrote:
>> Some upcoming cifs code, could make use of this, at least.
>
> Actually, it's probably not worth the dependency on ipv6
> for this small bit of code savings, so at least for cifs,
> this probably isn't useful.
Completely agreed.
prev parent reply other threads:[~2010-09-01 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 17:08 [net-next] ipv6: Export in6addr_any for use by modules Ben Greear
2010-08-31 23:01 ` Ben Greear
2010-09-01 18:07 ` David Miller [this message]
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=20100901.110710.67895761.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=greearb@candelatech.com \
--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).