From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Paul M Stillwell Jr <paul.m.stillwell.jr@intel.com>
Cc: Andrew Rybchenko <arybchenko@solarflare.com>,
dev@dpdk.org, ivan.boule@6wind.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ethdev: fix doxygen comment to be with structure
Date: Tue, 25 Sep 2018 16:43:16 +0100 [thread overview]
Message-ID: <10192dee-2874-b275-e254-c819beee6f1b@intel.com> (raw)
In-Reply-To: <5953600.MiQl7n2VzW@xps>
On 9/25/2018 2:44 PM, Thomas Monjalon wrote:
> 25/09/2018 16:31, Ferruh Yigit:
>> From: Paul M Stillwell Jr <paul.m.stillwell.jr@intel.com>
>>
>> The doxygen comment describing the rte_eth_dev_info structure
>> was separated from the structure itself so move the comment
>> back to be with the structure.
>>
>> Fixes: 7238e63bce52 ("ethdev: add support for device offload capabilities")
>> Cc: ivan.boule@6wind.com
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Paul M Stillwell Jr <paul.m.stillwell.jr@intel.com>
>
> Good catch!
>
> Acked-by: Thomas Monjalon <thomas@monjalon.net>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-09-25 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 14:31 Ferruh Yigit
2018-09-25 13:44 ` Thomas Monjalon
2018-09-25 15:43 ` 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=10192dee-2874-b275-e254-c819beee6f1b@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ivan.boule@6wind.com \
--cc=paul.m.stillwell.jr@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).