public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: wenxu <wenxu@ucloud.cn>
To: pablo@netfilter.org
Cc: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] nft_flow_offload: Make flow offload work with vrf slave device correct
Date: Wed, 9 Jan 2019 10:52:04 +0800	[thread overview]
Message-ID: <0cbf054a-6948-0b36-19d2-5eff27b2dbd6@ucloud.cn> (raw)
In-Reply-To: <1546078225-22699-1-git-send-email-wenxu@ucloud.cn>

Hi pablo,

How about the status for this patch?
 

On 12/29/2018 6:10 PM, wenxu@ucloud.cn wrote:
> From: wenxu <wenxu@ucloud.cn>
>
> In the forward chain the iif is changed from slave device to master vrf
> device. It will lead the offload not match on lower slave device.
>
> This patch make the flollowing example can work correct
>
>

  reply	other threads:[~2019-01-09  2:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-29 10:10 [PATCH] nft_flow_offload: Make flow offload work with vrf slave device correct wenxu
2019-01-09  2:52 ` wenxu [this message]
2019-01-10  0:40 ` Pablo Neira Ayuso

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=0cbf054a-6948-0b36-19d2-5eff27b2dbd6@ucloud.cn \
    --to=wenxu@ucloud.cn \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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