From: Simon Horman <horms@kernel.org>
To: Suman Ghosh <sumang@marvell.com>
Cc: sgoutham@marvell.com, gakula@marvell.com, sbhatta@marvell.com,
hkelam@marvell.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, lcherian@marvell.com,
jerinj@marvell.com, simon.horman@corigine.com,
jesse.brandeburg@intel.com
Subject: Re: [net-next PATCH V3 0/2] octeontx2-af: TC flower offload changes
Date: Tue, 1 Aug 2023 13:55:31 +0200 [thread overview]
Message-ID: <ZMjys4e4/S/dtyj2@kernel.org> (raw)
In-Reply-To: <20230801053813.2857958-1-sumang@marvell.com>
On Tue, Aug 01, 2023 at 11:08:11AM +0530, Suman Ghosh wrote:
> This patchset includes minor code restructuring related to TC
> flower offload for outer vlan and adding support for TC inner
> vlan offload.
>
> Patch #1 Code restructure to handle TC flower outer vlan offload
>
> Patch #2 Add TC flower offload support for inner vlan
Hi Suman,
unfortunately this does not apply to current net-next.
Please considering rebasing and posting as v4.
--
pw-bot: changes-requested
next prev parent reply other threads:[~2023-08-01 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 5:38 [net-next PATCH V3 0/2] octeontx2-af: TC flower offload changes Suman Ghosh
2023-08-01 5:38 ` [net-next PATCH V3 1/2] octeontx2-af: Code restructure to handle TC outer VLAN offload Suman Ghosh
2023-08-01 5:38 ` [net-next PATCH V3 2/2] octeontx2-af: TC flower offload support for inner VLAN Suman Ghosh
2023-08-01 11:55 ` Simon Horman [this message]
2023-08-01 12:00 ` [EXT] Re: [net-next PATCH V3 0/2] octeontx2-af: TC flower offload changes Suman Ghosh
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=ZMjys4e4/S/dtyj2@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jerinj@marvell.com \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=simon.horman@corigine.com \
--cc=sumang@marvell.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).