From: David Miller <davem@davemloft.net>
To: yanghy@cn.fujitsu.com
Cc: netdev@vger.kernel.org, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH]ipv6:use ipv6_addr_type instead of __ipv6_addr_type
Date: Fri, 08 May 2009 00:44:20 -0700 (PDT) [thread overview]
Message-ID: <20090508.004420.22402966.davem@davemloft.net> (raw)
In-Reply-To: <4A038853.4020205@cn.fujitsu.com>
From: Yang Hongyang <yanghy@cn.fujitsu.com>
Date: Fri, 08 May 2009 09:18:11 +0800
> David Miller wrote:
>> From: Yang Hongyang <yanghy@cn.fujitsu.com>
>> Date: Thu, 07 May 2009 15:47:38 +0800
>>
>>> Although the function of these two functions are the same,we should use the
>>> encapsulation function of __ipv6_addr_type
>>>
>>> Signed-off-by: Yang Hongyang<yanghy@cn.fujitsu.com>
>>
>> Are you sure? ipv6_addr_type() masks out the upper 16-bits
>> of __ipv6_addr_type()'s return value, which is the scope.
>>
>> I'm not convinced that is what we want to do here.
>
> My advice here is that the function which has __ maybe shouldn't be directly used.
You're using vague terms like "advice" and "maybe" and this
only decreases my confidence in your change.
You're also not addressing my questions at all.
Two "_" characters at the beginning of the function's name says
nothing about whether these call sites want the scope bits present in
the return value they receive.
This seems like a completely pointless and mindless change,
and in fact might introduce bugs.
There is no way I'm applying this. You can't even explain if the
patch is correct or not. In fact, I doubt you even know.
next prev parent reply other threads:[~2009-05-08 7:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 7:47 [PATCH]ipv6:use ipv6_addr_type instead of __ipv6_addr_type Yang Hongyang
2009-05-07 21:59 ` David Miller
2009-05-08 1:18 ` Yang Hongyang
2009-05-08 7:44 ` David Miller [this message]
2009-05-08 7:48 ` David Miller
2009-05-08 8:18 ` Yang Hongyang
2009-05-08 8:13 ` Yang Hongyang
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=20090508.004420.22402966.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=yanghy@cn.fujitsu.com \
--cc=yoshfuji@linux-ipv6.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).