From: Boris Sukholitko <boris.sukholitko@broadcom.com>
To: David Ahern <dsahern@kernel.org>
Cc: netdev@vger.kernel.org, "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Jiri Pirko <jiri@resnulli.us>,
"Gustavo A . R . Silva" <gustavoars@kernel.org>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Eric Dumazet <edumazet@google.com>,
zhang kai <zhangkaiheb@126.com>,
Yoshiki Komachi <komachi.yoshiki@gmail.com>,
Ilya Lifshits <ilya.lifshits@broadcom.com>
Subject: Re: [PATCH iproute2-next v2 2/2] f_flower: Check args with num_of_vlans
Date: Tue, 26 Apr 2022 12:17:27 +0300 [thread overview]
Message-ID: <20220426091727.GA7354@noodle> (raw)
In-Reply-To: <20220426021111.GA25966@u2004-local>
[-- Attachment #1: Type: text/plain, Size: 576 bytes --]
On Mon, Apr 25, 2022 at 08:11:11PM -0600, David Ahern wrote:
> On Tue, Apr 12, 2022 at 01:03:43PM +0300, Boris Sukholitko wrote:
> > Having more than one vlan allows matching on the vlan tag parameters.
> > This patch changes vlan key validation to take number of vlan tags into
> > account.
> >
> > Signed-off-by: Boris Sukholitko <boris.sukholitko@broadcom.com>
> > ---
> > tc/f_flower.c | 41 +++++++++++++++++++++++------------------
> > 1 file changed, 23 insertions(+), 18 deletions(-)
> >
>
> does not apply cleanly to iproute2-next
Rebased in v3.
Thanks,
Boris.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4221 bytes --]
prev parent reply other threads:[~2022-04-26 9:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 10:03 [PATCH iproute2-next v2 0/2] f_flower: match on the number of vlan tags Boris Sukholitko
2022-04-12 10:03 ` [PATCH iproute2-next v2 1/2] f_flower: Add num of vlans parameter Boris Sukholitko
2022-04-12 10:03 ` [PATCH iproute2-next v2 2/2] f_flower: Check args with num_of_vlans Boris Sukholitko
2022-04-26 2:11 ` David Ahern
2022-04-26 9:17 ` Boris Sukholitko [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=20220426091727.GA7354@noodle \
--to=boris.sukholitko@broadcom.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=gustavoars@kernel.org \
--cc=ilya.lifshits@broadcom.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=komachi.yoshiki@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vladimir.oltean@nxp.com \
--cc=xiyou.wangcong@gmail.com \
--cc=zhangkaiheb@126.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).