From: David Miller <davem@davemloft.net>
To: ogerlitz@mellanox.com
Cc: jakub.kicinski@netronome.com, john.r.fastabend@intel.com,
jhs@mojatatu.com, roid@mellanox.com, jiri@mellanox.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next V3 7/7] net/sched: cls_bpf: Reflect HW offload status
Date: Wed, 15 Feb 2017 13:16:39 -0500 (EST) [thread overview]
Message-ID: <20170215.131639.2135113997581761666.davem@davemloft.net> (raw)
In-Reply-To: <1487148757-24809-8-git-send-email-ogerlitz@mellanox.com>
From: Or Gerlitz <ogerlitz@mellanox.com>
Date: Wed, 15 Feb 2017 10:52:37 +0200
> @@ -511,6 +517,9 @@ static int cls_bpf_change(struct net *net, struct sk_buff *in_skb,
> return ret;
> }
>
> + if (!(tc_in_hw(prog->gen_flags)))
Again, less parenthesis.
Thanks.
prev parent reply other threads:[~2017-02-15 18:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 8:52 [PATCH net-next V3 0/7] net/sched: Reflect HW offload status in classifiers Or Gerlitz
2017-02-15 8:52 ` [PATCH net-next V3 1/7] net/sched: cls_flower: Properly handle classifier flags dumping Or Gerlitz
2017-02-15 8:52 ` [PATCH net-next V3 2/7] net/sched: cls_matchall: Dump the classifier flags Or Gerlitz
2017-02-15 8:52 ` [PATCH net-next V3 3/7] net/sched: Reflect HW offload status Or Gerlitz
2017-02-15 16:19 ` Or Gerlitz
2017-02-15 18:28 ` Jakub Kicinski
2017-02-15 21:56 ` Or Gerlitz
2017-02-15 23:07 ` Jakub Kicinski
2017-02-16 8:17 ` Ido Schimmel
2017-02-17 4:23 ` Jakub Kicinski
2017-02-15 8:52 ` [PATCH net-next V3 4/7] net/sched: cls_flower: " Or Gerlitz
2017-02-15 8:52 ` [PATCH net-next V3 5/7] net/sched: cls_matchall: Reflect HW offloading status Or Gerlitz
2017-02-15 18:15 ` David Miller
2017-02-15 21:40 ` Or Gerlitz
2017-02-15 8:52 ` [PATCH net-next V3 6/7] net/sched: cls_u32: Reflect HW offload status Or Gerlitz
2017-02-15 18:16 ` David Miller
2017-02-15 8:52 ` [PATCH net-next V3 7/7] net/sched: cls_bpf: " Or Gerlitz
2017-02-15 18:16 ` David Miller [this message]
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=20170215.131639.2135113997581761666.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=jhs@mojatatu.com \
--cc=jiri@mellanox.com \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=roid@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 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).