From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>
Cc: Lance Richardson <lance.richardson@broadcom.com>,
Xiaoyun Li <xiaoyun.li@intel.com>,
Olivier Matz <olivier.matz@6wind.com>,
Ray Kinsella <mdr@ashroe.eu>, Neil Horman <nhorman@tuxdriver.com>,
Jerin Jacob <jerinj@marvell.com>,
Somnath Kotur <somnath.kotur@broadcom.com>,
Beilei Xing <beilei.xing@intel.com>, Jeff Guo <jia.guo@intel.com>,
David Christensen <drc@linux.vnet.ibm.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>,
Ruifeng Wang <ruifeng.wang@arm.com>,
Jingjing Wu <jingjing.wu@intel.com>,
Qiming Yang <qiming.yang@intel.com>,
Qi Zhang <qi.z.zhang@intel.com>,
Haiyue Wang <haiyue.wang@intel.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Rasesh Mody <rmody@marvell.com>,
Shahed Shaikh <shshaikh@marvell.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Jiawen Wu <jiawenwu@trustnetic.com>,
Jian Wang <jianwang@trustnetic.com>, dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] mbuf: rename outer ip checksum macro
Date: Tue, 2 Mar 2021 09:58:10 +0000 [thread overview]
Message-ID: <6a8fa623-7b90-a114-b08a-2a88d7cd1c1d@intel.com> (raw)
In-Reply-To: <CACZ4nhv00ZhbCasBYCR2rFT7dptsb0YBz9bNsS02nkKB=SW9Gg@mail.gmail.com>
On 2/26/2021 4:27 PM, Ajit Khaparde wrote:
> On Fri, Feb 26, 2021 at 8:01 AM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
>>
>> On 2/25/2021 2:31 PM, Lance Richardson wrote:
>>> Rename PKT_RX_EIP_CKSUM_BAD to PKT_RX_OUTER_IP_CKSUM_BAD and
>>> deprecate the original name. The new name is better aligned
>>> with existing PKT_RX_OUTER_* flags, which should help reduce
>>> confusion about its use.
>>>
>>> Suggested-by: Ferruh Yigit <ferruh.yigit@intel.com>
>>> Signed-off-by: Lance Richardson <lance.richardson@broadcom.com>
>>> ---
>>> v2:
>>> - Added deprecation note.
>>> - Changed old macro definition to use the new one.
>>>
>>
>> Carrying Andrew's ack from previous version:
>> Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
>>
>>
>> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
> Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2021-03-02 9:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 16:24 [dpdk-dev] [PATCH] " Lance Richardson
2021-02-25 6:52 ` Andrew Rybchenko
2021-02-25 14:31 ` [dpdk-dev] [PATCH v2] " Lance Richardson
2021-02-26 16:01 ` Ferruh Yigit
2021-02-26 16:27 ` Ajit Khaparde
2021-03-02 9:58 ` Ferruh Yigit [this message]
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=6a8fa623-7b90-a114-b08a-2a88d7cd1c1d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=beilei.xing@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=haiyue.wang@intel.com \
--cc=jerinj@marvell.com \
--cc=jia.guo@intel.com \
--cc=jianwang@trustnetic.com \
--cc=jiawenwu@trustnetic.com \
--cc=jingjing.wu@intel.com \
--cc=kirankumark@marvell.com \
--cc=konstantin.ananyev@intel.com \
--cc=lance.richardson@broadcom.com \
--cc=mdr@ashroe.eu \
--cc=ndabilpuram@marvell.com \
--cc=nhorman@tuxdriver.com \
--cc=olivier.matz@6wind.com \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=rmody@marvell.com \
--cc=ruifeng.wang@arm.com \
--cc=shshaikh@marvell.com \
--cc=somnath.kotur@broadcom.com \
--cc=xiaoyun.li@intel.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).