From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: Rami Rosen <ramirose@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] bpf: fix a typo
Date: Wed, 22 Aug 2018 15:25:54 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB977258E9FA461F@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <20180822144545.4384-1-ramirose@gmail.com>
> -----Original Message-----
> From: Rami Rosen [mailto:ramirose@gmail.com]
> Sent: Wednesday, August 22, 2018 3:46 PM
> To: dev@dpdk.org
> Cc: Ananyev, Konstantin <konstantin.ananyev@intel.com>; Rami Rosen <ramirose@gmail.com>
> Subject: [PATCH] bpf: fix a typo
>
> This trivial patch fixes a typo in rte_bpf_ethdev.h,
>
> Signed-off-by: Rami Rosen <ramirose@gmail.com>
> ---
> lib/librte_bpf/rte_bpf_ethdev.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/librte_bpf/rte_bpf_ethdev.h b/lib/librte_bpf/rte_bpf_ethdev.h
> index 31731e7a9..11d09cdc2 100644
> --- a/lib/librte_bpf/rte_bpf_ethdev.h
> +++ b/lib/librte_bpf/rte_bpf_ethdev.h
> @@ -75,7 +75,7 @@ rte_bpf_eth_tx_unload(uint16_t port, uint16_t queue);
> * @param prm
> * Parameters used to create and initialise the BPF exeution context.
> * @param flags
> - * Flags that define expected expected behavior of the loaded filter
> + * Flags that define expected behavior of the loaded filter
> * (i.e. jited/non-jited version to use).
> * @return
> * Zero on successful completion or negative error code otherwise.
> --
Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> 2.17.1
next prev parent reply other threads:[~2018-08-22 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 14:45 Rami Rosen
2018-08-22 15:25 ` Ananyev, Konstantin [this message]
2018-10-25 9:15 ` 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=2601191342CEEE43887BDE71AB977258E9FA461F@IRSMSX102.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=dev@dpdk.org \
--cc=ramirose@gmail.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).