patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Xiaolong Ye <xiaolong.ye@intel.com>
Cc: Olivier Matz <olivier.matz@6wind.com>,
	Konstantin Ananyev <konstantin.ananyev@intel.com>,
	dev@dpdk.org, haiyue.wang@intel.com, stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v2] mbuf: remove unused next member in dyn flag/field
Date: Thu, 11 Jun 2020 09:42:49 +0200	[thread overview]
Message-ID: <2135063.brjnbXG0BY@thomas> (raw)
In-Reply-To: <20200609071256.59837-1-xiaolong.ye@intel.com>

09/06/2020 09:12, Xiaolong Ye:
> TAILQ_ENTRY next is not needed in struct mbuf_dynfield_elt and
> mbuf_dynflag_elt, since they are actually chained by rte_tailq_entry's
> next field when calling TAILQ_INSERT_TAIL(mbuf_dynfield/dynflag_list, te,
> next).
> 
> Fixes: 4958ca3a443a ("mbuf: support dynamic fields and flags")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Xiaolong Ye <xiaolong.ye@intel.com>
> Acked-by: Olivier Matz <olivier.matz@6wind.com>

Applied, thanks



  reply	other threads:[~2020-06-11  7:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-09  5:29 [dpdk-stable] [PATCH] mbuf: remove unused next member Xiaolong Ye
2020-06-09  7:12 ` [dpdk-stable] [PATCH v2] mbuf: remove unused next member in dyn flag/field Xiaolong Ye
2020-06-11  7:42   ` Thomas Monjalon [this message]
2020-06-09  7:17 ` [dpdk-stable] [PATCH] mbuf: remove unused next member Olivier Matz
2020-06-09  7:15   ` Ye Xiaolong
2020-06-09 15:29     ` [dpdk-stable] [dpdk-dev] " Stephen Hemminger
2020-06-10  0:54       ` Ye Xiaolong

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=2135063.brjnbXG0BY@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=haiyue.wang@intel.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=olivier.matz@6wind.com \
    --cc=stable@dpdk.org \
    --cc=xiaolong.ye@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).