patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Yongseok Koh <yskoh@mellanox.com>
To: Yuanhan Liu <yliu@fridaylinux.org>
Cc: "luca.boccassi@gmail.com" <luca.boccassi@gmail.com>,
	Shahaf Shuler <shahafs@mellanox.com>,
	Wisam Monther <wisamm@mellanox.com>,
	dpdk stable <stable@dpdk.org>
Subject: [dpdk-stable] A missing mlx5 patch for stable 17.11
Date: Wed, 23 May 2018 21:07:56 +0000	[thread overview]
Message-ID: <B403D037-DECE-4EB8-A809-4E662E1A12AC@mellanox.com> (raw)

Hi, Yuanhan

There's one missing patch from upstream repo. It is because the patch doesn't
have Cc tag. I should've asked when I acked it.

Please push this one to the 17.11 queue for the next available release.
I confirmed it can be applied without any conflict.


commit 0915e287a6a7ed884a3de198f08926d8418366d4
Author: Bin Huang <bin.huang@hxt-semitech.com>
Date:   Fri Mar 30 13:13:38 2018 +0800

    net/mlx5: add packet type index for TCP ack

    According to CQE format:
    - l4_hdr_type:
         0 - None
         1 - TCP header was present in the packet
         2 - UDP header was present in the packet
         3 - TCP header was present in the packet with Empty
             TCP ACK indication. (TCP packet <ACK> flag is set,
             and packet carries no data)
         4 - TCP header was present in the packet with TCP ACK indication.
             (TCP packet <ACK> flag is set, and packet carries data).

    A packet should be identified as TCP packet if l4_hdr_type is 1, 3 or 4.
    Add corresponding idx of TCP ACK to ptype table.

    previous discussion:
    https://www.mail-archive.com/users@dpdk.org/msg02980.html

    Signed-off-by: Bin Huang <bin.huang@hxt-semitech.com>
    Acked-by: Yongseok Koh <yskoh@mellanox.com>



Thanks,
Yongseok

             reply	other threads:[~2018-05-23 21:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-23 21:07 Yongseok Koh [this message]
2018-05-27  3:15 ` Yuanhan Liu
2018-05-29  6:51   ` Shahaf Shuler
2018-06-02  5:14     ` Yuanhan Liu

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=B403D037-DECE-4EB8-A809-4E662E1A12AC@mellanox.com \
    --to=yskoh@mellanox.com \
    --cc=luca.boccassi@gmail.com \
    --cc=shahafs@mellanox.com \
    --cc=stable@dpdk.org \
    --cc=wisamm@mellanox.com \
    --cc=yliu@fridaylinux.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).