From: Thomas Monjalon <thomas@monjalon.net>
To: Gage Eads <gage.eads@intel.com>
Cc: dev@dpdk.org, olivier.matz@6wind.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ring: fix namesize macro documentation block
Date: Thu, 04 Apr 2019 17:45:49 +0200 [thread overview]
Message-ID: <1689908.LWGM3x1bQc@xps> (raw)
Message-ID: <20190404154549.b-mvFbZOgep2xXAHdLVF9wqMMENZMoR-vYTqGTQ70pA@z> (raw)
In-Reply-To: <20190404123454.16755-1-gage.eads@intel.com>
04/04/2019 14:34, Gage Eads:
> '/**<' style comments apply to the previous member, which caused doxygen to
> emit the RTE_RING_NAMESIZE documentation for RTE_RING_MZ_PREFIX.
>
> Fixes: 38c9817ee1d8 ("mempool: adjust name size in related data types")
> Cc: stable@dpdk.org
>
> Signed-off-by: Gage Eads <gage.eads@intel.com>
Applied, thanks
next prev parent reply other threads:[~2019-04-04 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 12:34 Gage Eads
2019-04-04 12:34 ` Gage Eads
2019-04-04 15:45 ` Thomas Monjalon [this message]
2019-04-04 15:45 ` Thomas Monjalon
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=1689908.LWGM3x1bQc@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=gage.eads@intel.com \
--cc=olivier.matz@6wind.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).