patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Konstantin Ananyev <konstantin.ananyev@intel.com>
Cc: dev@dpdk.org, stable@dpdk.org, ryan.e.hall@intel.com,
	alexander.v.gutkin@intel.com
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v2 0/2] ip_frag: two fixes in reassembly code
Date: Tue, 06 Nov 2018 01:58:46 +0100	[thread overview]
Message-ID: <7228016.KtrQZcpx88@xps> (raw)
In-Reply-To: <1541420338-300-1-git-send-email-konstantin.ananyev@intel.com>

05/11/2018 13:18, Konstantin Ananyev:
> Fix 2 issues reported in reassembly code path.
> 
> Konstantin Ananyev (2):
>   ip_frag: check fragment length of incoming packet
>   ip_frag: use key length for key comparision

Applied, thanks

  reply	other threads:[~2018-11-06  0:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-05 10:26 [dpdk-stable] [PATCH " Konstantin Ananyev
2018-11-05 10:26 ` [dpdk-stable] [PATCH 1/2] ip_frag: check fragment length of incoming packet Konstantin Ananyev
2018-11-05 11:37   ` Thomas Monjalon
2018-11-05 10:26 ` [dpdk-stable] [PATCH 2/2] ip_frag: use key length for key comparision Konstantin Ananyev
2018-11-05 12:11 ` [dpdk-stable] [PATCH v2 0/2] ip_frag: two fixes in reassembly code Konstantin Ananyev
2018-11-05 12:11 ` [dpdk-stable] [PATCH v2 1/2] ip_frag: check fragment length of incoming packet Konstantin Ananyev
2018-11-05 12:11 ` [dpdk-stable] [PATCH 2/2] ip_frag: use key length for key comparision Konstantin Ananyev
2018-11-05 12:18 ` [dpdk-stable] [PATCH v2 0/2] ip_frag: two fixes in reassembly code Konstantin Ananyev
2018-11-06  0:58   ` Thomas Monjalon [this message]
2018-11-05 12:18 ` [dpdk-stable] [PATCH v2 1/2] ip_frag: check fragment length of incoming packet Konstantin Ananyev
2018-11-05 12:18 ` [dpdk-stable] [PATCH v2 2/2] ip_frag: use key length for key comparision Konstantin Ananyev
2018-11-06 10:53   ` [dpdk-stable] [dpdk-dev] " Burakov, Anatoly
2018-11-06 11:41     ` Ananyev, Konstantin

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=7228016.KtrQZcpx88@xps \
    --to=thomas@monjalon.net \
    --cc=alexander.v.gutkin@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=ryan.e.hall@intel.com \
    --cc=stable@dpdk.org \
    /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).