public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Lobakin <aleksander.lobakin@intel.com>
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>
Subject: Re: [net PATCH V2] octeontx2-pf: Add additional check for MCAM rules.
Date: Mon, 3 Jul 2023 18:32:23 +0200	[thread overview]
Message-ID: <b6501c25-e40a-ba84-734a-577da0c2ab7a@intel.com> (raw)
In-Reply-To: <20230703095600.2048397-1-sumang@marvell.com>

From: Suman Ghosh <sumang@marvell.com>
Date: Mon, 3 Jul 2023 15:26:00 +0530

> Re: [net PATCH V2] octeontx2-pf: Add additional check for MCAM rules.

Please no periods at the end of commit messages.

> Due to hardware limitation, MCAM drop rule with
> ether_type == 802.1Q and vlan_id == 0 is not supported. Hence rejecting
> such rules.
> 
> Signed-off-by: Suman Ghosh <sumang@marvell.com>

Targeted to net/fixes with no "Fixes:" tagging the blamed commit.

> ---
> Changes since v1:
> - Updated commit message
> 
>  .../net/ethernet/marvell/octeontx2/nic/otx2_flows.c |  7 +++++++
>  .../net/ethernet/marvell/octeontx2/nic/otx2_tc.c    | 13 +++++++++++++
>  2 files changed, 20 insertions(+)

[...]

Thanks,
Olek

  reply	other threads:[~2023-07-03 16:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-03  9:56 [net PATCH V2] octeontx2-pf: Add additional check for MCAM rules Suman Ghosh
2023-07-03 16:32 ` Alexander Lobakin [this message]
2023-07-03 17:42   ` [EXT] " 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=b6501c25-e40a-ba84-734a-577da0c2ab7a@intel.com \
    --to=aleksander.lobakin@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gakula@marvell.com \
    --cc=hkelam@marvell.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sbhatta@marvell.com \
    --cc=sgoutham@marvell.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