From: Jakub Kicinski <kuba@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>, <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 V4 0/2] octeontx2-af: TC flower offload changes
Date: Wed, 2 Aug 2023 19:34:24 -0700 [thread overview]
Message-ID: <20230802193424.79377f40@kernel.org> (raw)
In-Reply-To: <20230801153657.2875497-1-sumang@marvell.com>
On Tue, 1 Aug 2023 21:06:55 +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
>
> Suman Ghosh (2):
> octeontx2-af: Code restructure to handle TC outer VLAN offload
> octeontx2-af: TC flower offload support for inner VLAN
>
> v4 changes:
> Resolved conflicts with 'main' branch
Still does not apply.
After you git format-patch the patches check out net-next/main
and git am /path/to/patches..
--
pw-bot: cr
prev parent reply other threads:[~2023-08-03 2:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 15:36 [net-next PATCH V4 0/2] octeontx2-af: TC flower offload changes Suman Ghosh
2023-08-01 15:36 ` [net-next PATCH V4 1/2] octeontx2-af: Code restructure to handle TC outer VLAN offload Suman Ghosh
2023-08-01 15:36 ` [net-next PATCH V4 2/2] octeontx2-af: TC flower offload support for inner VLAN Suman Ghosh
2023-08-03 2:34 ` Jakub Kicinski [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=20230802193424.79377f40@kernel.org \
--to=kuba@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.