From: Thomas Monjalon <thomas@monjalon.net>
To: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Cc: olivier.matz@6wind.com, david.marchand@redhat.com, dev@dpdk.org,
nd@arm.com
Subject: Re: [dpdk-dev] [PATCH] doc: add rte_ring_xxx_elem introduction to rel notes
Date: Sat, 15 Feb 2020 15:54:34 +0100 [thread overview]
Message-ID: <4823455.jY9Djz4Zq0@xps> (raw)
In-Reply-To: <20200126174029.616-1-honnappa.nagarahalli@arm.com>
26/01/2020 18:40, Honnappa Nagarahalli:
> Added introduction of rte_ring_xxx_elem APIs to release notes.
Fixes: cc4b218790f6 ("ring: support configurable element size")
> Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Applied, thanks
next prev parent reply other threads:[~2020-02-15 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-26 17:40 Honnappa Nagarahalli
2020-02-15 14:54 ` Thomas Monjalon [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-25 15:10 Honnappa Nagarahalli
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=4823455.jY9Djz4Zq0@xps \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=nd@arm.com \
--cc=olivier.matz@6wind.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).