From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: Suman Ghosh <sumang@marvell.com>, <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>
Subject: Re: [net-next PATCH V2 1/2] octeontx2-af: Code restructure to handle TC outer VLAN offload
Date: Mon, 31 Jul 2023 10:20:29 -0700 [thread overview]
Message-ID: <d30ccfb9-5632-de27-fd2e-07b93adaad42@intel.com> (raw)
In-Reply-To: <20230730143107.2845172-2-sumang@marvell.com>
On 7/30/2023 7:31 AM, Suman Ghosh wrote:
> Moved the TC outer VLAN offload support to a separate function.
> This change is done to handle all VLAN related changes cleanly from
> a dedicated function.
>
> Signed-off-by: Suman Ghosh <sumang@marvell.com>
Reviewed-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
next prev parent reply other threads:[~2023-07-31 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 14:31 [net-next PATCH V2 0/2] octeontx2-af: TC flower offload changes Suman Ghosh
2023-07-30 14:31 ` [net-next PATCH V2 1/2] octeontx2-af: Code restructure to handle TC outer VLAN offload Suman Ghosh
2023-07-31 17:20 ` Jesse Brandeburg [this message]
2023-07-30 14:31 ` [net-next PATCH V2 2/2] octeontx2-af: TC flower offload support for inner VLAN Suman Ghosh
2023-07-31 17:24 ` Jesse Brandeburg
-- strict thread matches above, loose matches on Subject: below --
2023-07-30 8:00 [net-next PATCH V2 0/2] octeontx2-af: Code restructuting and new Suman Ghosh
2023-07-30 8:00 ` [net-next PATCH V2 1/2] octeontx2-af: Code restructure to handle TC outer VLAN offload 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=d30ccfb9-5632-de27-fd2e-07b93adaad42@intel.com \
--to=jesse.brandeburg@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jerinj@marvell.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).