From: Gu Zheng <guz.fnst@cn.fujitsu.com>
To: Joe Perches <joe@perches.com>
Cc: "David S. Miller" <davem@davemloft.net>, <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] net: introduce helper macro for_each_cmsghdr
Date: Thu, 11 Dec 2014 09:11:08 +0800 [thread overview]
Message-ID: <5488EF2C.6010502@cn.fujitsu.com> (raw)
In-Reply-To: <1418223106.18092.1.camel@perches.com>
Hi Joe,
On 12/10/2014 10:51 PM, Joe Perches wrote:
> On Wed, 2014-12-10 at 16:15 +0800, Gu Zheng wrote:
>> On 12/10/2014 02:56 PM, Joe Perches wrote:
>>> On Wed, 2014-12-10 at 13:36 +0800, Gu Zheng wrote:
>>>> Introduce helper macro for_each_cmsghdr as a wrapper of the enumerating
>>>> cmsghdr from msghdr, just cleanup.
>>>
>>> This looks nicer.
>>> Ideally this would have used: [PATCH V3] as the subject
>>
>> The previous v2 thread was marked as mistake, so this is the really active
>> v2 version.
>
> A buggy submitted version is still a version.
> Using an incremented version number helps.
Got it, this can also avoid some unnecessary misreading.
Thanks for your suggestion.
Regards,
Gu
>
>
next prev parent reply other threads:[~2014-12-11 1:11 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 [this message]
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
-- 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=5488EF2C.6010502@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).