DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Jerin Jacob <jerinj@marvell.com>, Anoob Joseph <anoobj@marvell.com>
Cc: Akhil Goyal <gakhil@marvell.com>,
	dev@dpdk.org, Ankur Dwivedi <adwivedi@marvell.com>,
	Tejasree Kondoj <ktejasree@marvell.com>,
	dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] common/cpt: add checks for offset overflow
Date: Tue, 11 May 2021 15:29:23 +0200	[thread overview]
Message-ID: <9006395.vvp0iXuPjc@thomas> (raw)
In-Reply-To: <1620639840-89-1-git-send-email-anoobj@marvell.com>

10/05/2021 11:44, Anoob Joseph:
> Add checks to catch overflow of any offsets. Offset control word
> specifies,
> 
> 1. 16 bits encryption offset
> 2. 8 bits IV offset
> 3. 8 bits auth offset
> 
> Signed-off-by: Anoob Joseph <anoobj@marvell.com>

Should it be merged in DPDK 21.05-rc3, or wait for 21.08?




  reply	other threads:[~2021-05-11 13:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10  9:44 Anoob Joseph
2021-05-11 13:29 ` Thomas Monjalon [this message]
2021-05-11 13:39   ` [dpdk-dev] [EXT] " Anoob Joseph
2021-07-06 19:43   ` Akhil Goyal

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=9006395.vvp0iXuPjc@thomas \
    --to=thomas@monjalon.net \
    --cc=adwivedi@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=ktejasree@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).