From: Jerin Jacob <jerinjacobk@gmail.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, stable@dpdk.org,
Erik Gabriel Carrillo <erik.g.carrillo@intel.com>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>,
Pavan Nikhilesh <pbhagavatula@marvell.com>
Subject: Re: [PATCH] doc: fix reference to event timer header
Date: Thu, 23 Feb 2023 19:56:54 +0530 [thread overview]
Message-ID: <CALBAE1PnOS36vhcQFZcc=0AHX3si6p7FUAM6zZLuiPxhdf01vQ@mail.gmail.com> (raw)
In-Reply-To: <20230220144711.2698257-1-david.marchand@redhat.com>
On Mon, Feb 20, 2023 at 8:17 PM David Marchand
<david.marchand@redhat.com> wrote:
>
> The event timer header is rte_event_timer_adapter.h.
> Besides, we don't need to detail the full path to such a header.
>
> Fixes: 30e7fbd62839 ("doc: add event timer adapter guide")
> Cc: stable@dpdk.org
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
Applied to dpdk-next-net-eventdev/for-main. Thanks
> ---
> doc/guides/prog_guide/event_timer_adapter.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/guides/prog_guide/event_timer_adapter.rst b/doc/guides/prog_guide/event_timer_adapter.rst
> index 4e07f0cc23..2a15ed8f5c 100644
> --- a/doc/guides/prog_guide/event_timer_adapter.rst
> +++ b/doc/guides/prog_guide/event_timer_adapter.rst
> @@ -35,7 +35,7 @@ device upon timer expiration.
>
> The Event Timer Adapter API represents each event timer with a generic struct,
> which contains an event and user metadata. The ``rte_event_timer`` struct is
> -defined in ``lib/event/librte_event_timer_adapter.h``.
> +defined in ``rte_event_timer_adapter.h``.
>
> .. _timer_expiry_event:
>
> --
> 2.39.2
>
prev parent reply other threads:[~2023-02-23 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 14:47 David Marchand
2023-02-23 14:26 ` Jerin Jacob [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='CALBAE1PnOS36vhcQFZcc=0AHX3si6p7FUAM6zZLuiPxhdf01vQ@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=erik.g.carrillo@intel.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=pbhagavatula@marvell.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).