patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Jens Freimann <jfreimann@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev@dpdk.org, ybrustin@cisco.com, tiwei.bie@intel.com,
	david.marchand@redhat.com, stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v3 3/4] net/virtio: fix segment data len in mergeable packed Rx path
Date: Wed, 5 Jun 2019 13:16:10 +0200	[thread overview]
Message-ID: <20190605111610.lxfhzrbgvoy7iuuo@jenstp.localdomain> (raw)
In-Reply-To: <20190605100039.18029-4-maxime.coquelin@redhat.com>

On Wed, Jun 05, 2019 at 12:00:38PM +0200, Maxime Coquelin wrote:
>Head segment data_len field is wrongly summed with the length
>of all the segments of the chain, whereas it should be the
>length of of the first segment only.

s/of of/of/

Reviewed-by: Jens Freimann <jfreimann@redhat.com> 

regards,
Jens 

  reply	other threads:[~2019-06-05 11:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-05 10:00 [dpdk-stable] [PATCH v3 0/4] et/virtio: Fix packet segmentation bug Maxime Coquelin
2019-06-05 10:00 ` [dpdk-stable] [PATCH v3 1/4] net/virtio: fix segmented packet issue in in-order Rx path Maxime Coquelin
2019-06-05 10:00 ` [dpdk-stable] [PATCH v3 2/4] net/virtio: fix segmented packet issue in mergeable " Maxime Coquelin
2019-06-05 10:00 ` [dpdk-stable] [PATCH v3 3/4] net/virtio: fix segment data len in mergeable packed " Maxime Coquelin
2019-06-05 11:16   ` Jens Freimann [this message]
2019-06-05 11:34     ` [dpdk-stable] [dpdk-dev] " Maxime Coquelin
2019-06-05 10:00 ` [dpdk-stable] [PATCH v3 4/4] net/virtio: remove useless pointers checks Maxime Coquelin
2019-06-06  7:15   ` [dpdk-stable] [dpdk-dev] " Ye Xiaolong
2019-06-06  7:31     ` Maxime Coquelin
2019-06-05 13:25 ` [dpdk-stable] [PATCH v3 0/4] et/virtio: Fix packet segmentation bug Tiwei Bie
2019-06-06  9:31 ` Maxime Coquelin

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=20190605111610.lxfhzrbgvoy7iuuo@jenstp.localdomain \
    --to=jfreimann@redhat.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=maxime.coquelin@redhat.com \
    --cc=stable@dpdk.org \
    --cc=tiwei.bie@intel.com \
    --cc=ybrustin@cisco.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).