netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jianbo Liu <jianbol@mellanox.com>
To: Edward Cree <ecree@solarflare.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: [RFC PATCH net-next 3/3] flow_offload: support CVLAN match
Date: Tue, 14 May 2019 08:53:00 +0000	[thread overview]
Message-ID: <20190514085255.GA5175@mellanox.com> (raw)
In-Reply-To: <62a0f0f9-d576-baa6-f34d-f4875214ea7d@solarflare.com>

The 05/13/2019 14:28, Edward Cree wrote:
> On 13/05/2019 13:54, Jianbo Liu wrote:
> > Could you please push to 5.1 and 5.0-stable? The original patch brought a bug
> > in mlx5_core driver. Need your patch to fix.
> >
> > --- a/drivers/net/ethernet/mellanox/mlx5/core/en_tc.c
> > +++ b/drivers/net/ethernet/mellanox/mlx5/core/en_tc.c
> > @@ -1615,7 +1615,7 @@ static int __parse_cls_flower(struct mlx5e_priv *priv,
> >         if (flow_rule_match_key(rule, FLOW_DISSECTOR_KEY_CVLAN)) {
> >                 struct flow_match_vlan match;
> >
> > -               flow_rule_match_vlan(rule, &match);
> > +               flow_rule_match_cvlan(rule, &match);
> >                 if (match.mask->vlan_id ||
> >                     match.mask->vlan_priority ||
> >                     match.mask->vlan_tpid) {
> >
> > Thanks!
> My patch will be more easily accepted with a user in-tree, so could
>  you give this fix a commit message and SOB?  Then I'll roll it into
>  my next posting of this series, thanks!
> 

OK, I will send the patch later, thanks!

Jianbo

      reply	other threads:[~2019-05-14  8:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-03 15:08 [RFC PATCH net-next 3/3] flow_offload: support CVLAN match Edward Cree
2019-05-13 12:54 ` Jianbo Liu
2019-05-13 13:28   ` Edward Cree
2019-05-14  8:53     ` Jianbo Liu [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=20190514085255.GA5175@mellanox.com \
    --to=jianbol@mellanox.com \
    --cc=ecree@solarflare.com \
    --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).