From: Jamal Hadi Salim <jhs@mojatatu.com>
To: Alexander Aring <aring@mojatatu.com>
Cc: xiyou.wangcong@gmail.com, jiri@resnulli.us,
netdev@vger.kernel.org, eric.dumazet@gmail.com, bjb@mojatatu.com,
Yotam Gigi <yotamg@mellanox.com>
Subject: Re: [PATCH net-next 1/3] sched: act: ife: move encode/decode check to init
Date: Thu, 12 Oct 2017 21:38:20 -0400 [thread overview]
Message-ID: <df414888-a723-f6df-f703-d83045ab25dd@mojatatu.com> (raw)
In-Reply-To: <20171011211608.22692-2-aring@mojatatu.com>
On 17-10-11 05:16 PM, Alexander Aring wrote:
> This patch adds the check of the two possible ife handlings encode
> and decode to the init callback. The decode value is for usability
> aspect and used in userspace code only. The current code offers encode
> else decode only. This patch avoids any other option than this.
>
> Signed-off-by: Alexander Aring <aring@mojatatu.com>
Acked-by: Jamal Hadi Salim <jhs@mojatatu.com>
cheers,
jamal
next prev parent reply other threads:[~2017-10-13 1:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 21:16 [PATCH net-next 0/3] sched: act: ife: UAPI checks and performance tweaks Alexander Aring
2017-10-11 21:16 ` [PATCH net-next 1/3] sched: act: ife: move encode/decode check to init Alexander Aring
2017-10-13 1:38 ` Jamal Hadi Salim [this message]
2017-10-11 21:16 ` [PATCH net-next 2/3] sched: act: ife: migrate to use per-cpu counters Alexander Aring
2017-10-13 1:39 ` Jamal Hadi Salim
2017-10-11 21:16 ` [PATCH net-next 3/3] sched: act: ife: update parameters via rcu handling Alexander Aring
2017-10-13 1:39 ` Jamal Hadi Salim
2017-10-13 5:23 ` [PATCH net-next 0/3] sched: act: ife: UAPI checks and performance tweaks David Miller
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=df414888-a723-f6df-f703-d83045ab25dd@mojatatu.com \
--to=jhs@mojatatu.com \
--cc=aring@mojatatu.com \
--cc=bjb@mojatatu.com \
--cc=eric.dumazet@gmail.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
--cc=yotamg@mellanox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.