From: Gu Zheng <guz.fnst@cn.fujitsu.com>
To: David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<joe@perches.com>
Subject: Re: [PATCH v2] net: introduce helper macro for_each_cmsghdr
Date: Thu, 11 Dec 2014 09:50:02 +0800 [thread overview]
Message-ID: <5488F84A.8090303@cn.fujitsu.com> (raw)
In-Reply-To: <20141210.204703.1525194278635097457.davem@davemloft.net>
Hi David,
On 12/11/2014 09:47 AM, David Miller wrote:
> From: Gu Zheng <guz.fnst@cn.fujitsu.com>
> Date: Thu, 11 Dec 2014 09:05:59 +0800
>
>> IMO, the user-land programs need to be build with the matched
>> headers separately.
>
> You absolutely cannot provide this new interface to userland and
> expect programs to be able to just use it, it's non-standard and does
> not exist in older headers.
Got it, sorry for my mistake, and thanks for your correction.
>
> I do not want this new interface available to userland programs.
> They can just open-code the list traversal just like every program
> in history has had to do since BSD UNIX.
Agree. Let's leave the user-land ones as they are.
I'll send a new version (without changing user-land ones) soon.
Best regards,
Gu
> .
>
next prev parent reply other threads:[~2014-12-11 1:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 5:36 [PATCH v2] net: introduce helper macro for_each_cmsghdr Gu Zheng
2014-12-10 6:56 ` Joe Perches
2014-12-10 8:15 ` Gu Zheng
2014-12-10 14:51 ` Joe Perches
2014-12-11 1:11 ` Gu Zheng
2014-12-10 18:48 ` David Miller
2014-12-10 19:44 ` David Miller
2014-12-11 1:05 ` Gu Zheng
2014-12-11 1:47 ` David Miller
2014-12-11 1:50 ` Gu Zheng [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-10 1:39 Gu Zheng
2014-12-10 1:56 ` Gu Zheng
2014-12-10 2:01 ` Joe Perches
2014-12-10 2:02 ` Gu Zheng
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=5488F84A.8090303@cn.fujitsu.com \
--to=guz.fnst@cn.fujitsu.com \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--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).