From: Yang Hongyang <yanghy@cn.fujitsu.com>
To: David Miller <davem@davemloft.net>
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 16:18:11 +0800 [thread overview]
Message-ID: <4A03EAC3.1010601@cn.fujitsu.com> (raw)
In-Reply-To: <20090508.004835.216058418.davem@davemloft.net>
David Miller wrote:
> From: David Miller <davem@davemloft.net>
> Date: Fri, 08 May 2009 00:44:20 -0700 (PDT)
>
>> 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.
>
> I also want to address this statement on it's own, it's simply
> not true.
>
> "__" means "think carefully before using this function", or "this
> function requires a special environment for proper usage"
>
> It DOES NOT mean "do not use directly." It's never meant this.
I was wrong,thank you for your patience to explain this.
>
> So ever basis for your patch is fundamentally flawed.
>
>
--
Regards
Yang Hongyang
next prev parent reply other threads:[~2009-05-08 8:17 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
2009-05-08 7:48 ` David Miller
2009-05-08 8:18 ` Yang Hongyang [this message]
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=4A03EAC3.1010601@cn.fujitsu.com \
--to=yanghy@cn.fujitsu.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--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).