From: Jiri Pirko <jiri@resnulli.us>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
xiyou.wangcong@gmail.com, eric.dumazet@gmail.com,
horms@verge.net.au, dsahern@gmail.com
Subject: Re: [PATCH net-next v12 1/4] net netlink: Add new type NLA_BITFIELD32
Date: Mon, 31 Jul 2017 14:21:06 +0200 [thread overview]
Message-ID: <20170731122106.GD1883@nanopsycho> (raw)
In-Reply-To: <fa171203-adab-9950-8241-dd5b3a70fe0a@mojatatu.com>
Mon, Jul 31, 2017 at 02:03:55PM CEST, jhs@mojatatu.com wrote:
>On 17-07-31 02:38 AM, Jiri Pirko wrote:
>> Sun, Jul 30, 2017 at 09:59:10PM CEST, jhs@mojatatu.com wrote:
>> > Jiri,
>> >
>> > This is getting exhausting, seriously.
>> > I posted the code you are commenting one two days ago so i dont have to
>> > repost.
>>
>> And I commented on the "*u32 = *u32" thing. But you ignored it. Pardon
>> me for mentioning that again now :/
>>
>
>You commented on *u32 assignment from *void which i fixed. I
>intentionally selected the different assignment names to reflect
>meaning. Had you commented earlier - although I would have found
Yep, I don't understand why the function arg cannot have the desired
name right away. Also, I don't understand why you don't just have u32
instead of pointer as a local variable, if you really needed this local
variable. Ok, I admit that ":)" is probably not intuitive comment.
Will be more blunt next time.
>it disagreable - I would have fixed that too. Jiri, you need to be
>more tolerant so progress can be made at times.
I don't think so. I believe that it is really important that code can be
read nicely. If we don't do it, it will be just mess (like it is in lot
of net/sched/ places).
>
>>
>> >
>> > On D. Ahern: I dont think we are disagreeing anymore on the need to
>> > generalize the check. He is saying it should be a helper and I already
>> > had the validation data; either works. I dont see the gapping need
>> > to remove the validation data.
>>
>> DavidA? Your opinion.
>>
>
>With DavidA(reading his response) - the issue is one of taste.
>Again either approach is fine. You can call helpers for every user
>or make them invoked behind the scenes.
>Again - like all your comments on code taste which I addressed, I
>would have made that change if the comment had come in earlier. I got
>exhausted. Imagine how a newbie corporate guy wouldve felt after this.
That's how it is.
next prev parent reply other threads:[~2017-07-31 12:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-30 17:24 [PATCH net-next v12 0/4] net sched actions: improve dump performance Jamal Hadi Salim
2017-07-30 17:24 ` [PATCH net-next v12 1/4] net netlink: Add new type NLA_BITFIELD32 Jamal Hadi Salim
2017-07-30 18:42 ` Jiri Pirko
2017-07-30 19:59 ` Jamal Hadi Salim
2017-07-31 2:27 ` David Ahern
2017-07-31 6:38 ` Jiri Pirko
2017-07-31 12:03 ` Jamal Hadi Salim
2017-07-31 12:21 ` Jiri Pirko [this message]
2017-07-30 17:24 ` [PATCH net-next v12 2/4] net sched actions: Use proper root attribute table for actions Jamal Hadi Salim
2017-07-30 18:44 ` Jiri Pirko
2017-07-30 17:24 ` [PATCH net-next v12 3/4] net sched actions: dump more than TCA_ACT_MAX_PRIO actions per batch Jamal Hadi Salim
2017-07-30 19:05 ` Jiri Pirko
2017-07-30 17:24 ` [PATCH net-next v12 4/4] net sched actions: add time filter for action dumping Jamal Hadi Salim
2017-07-30 19:06 ` Jiri Pirko
2017-07-31 2:28 ` [PATCH net-next v12 0/4] net sched actions: improve dump performance David Miller
2017-07-31 12:06 ` Jamal Hadi Salim
2017-07-31 23:43 ` Stephen Hemminger
2017-08-01 3:54 ` Stephen Hemminger
2017-08-01 11:05 ` Jamal Hadi Salim
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=20170731122106.GD1883@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@verge.net.au \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
/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