From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] mem: fix typo in local function name
Date: Wed, 2 May 2018 10:28:16 +0100 [thread overview]
Message-ID: <fbfaf56b-40b1-f753-4520-993a0691baf8@intel.com> (raw)
In-Reply-To: <20180501193852.1728-1-thomas@monjalon.net>
On 01-May-18 8:38 PM, Thomas Monjalon wrote:
> Fixes: 582bed1e1d1d ("mem: support mapping hugepages at runtime")
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> lib/librte_eal/linuxapp/eal/eal_memalloc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lib/librte_eal/linuxapp/eal/eal_memalloc.c b/lib/librte_eal/linuxapp/eal/eal_memalloc.c
> index 360d8f73c..ace2bcf3e 100644
> --- a/lib/librte_eal/linuxapp/eal/eal_memalloc.c
> +++ b/lib/librte_eal/linuxapp/eal/eal_memalloc.c
> @@ -143,7 +143,7 @@ prepare_numa(int *oldpolicy, struct bitmask *oldmask, int socket_id)
> }
>
> static void
> -resotre_numa(int *oldpolicy, struct bitmask *oldmask)
> +restore_numa(int *oldpolicy, struct bitmask *oldmask)
> {
> RTE_LOG(DEBUG, EAL,
> "Restoring previous memory policy: %d\n", *oldpolicy);
> @@ -889,7 +889,7 @@ eal_memalloc_alloc_seg_bulk(struct rte_memseg **ms, int n_segs, size_t page_sz,
>
> #ifdef RTE_EAL_NUMA_AWARE_HUGEPAGES
> if (have_numa)
> - resotre_numa(&oldpolicy, oldmask);
> + restore_numa(&oldpolicy, oldmask);
> #endif
> return ret;
> }
>
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
(tempted to say "Akced"...)
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-05-02 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 19:38 Thomas Monjalon
2018-05-02 9:28 ` Burakov, Anatoly [this message]
2018-05-02 9:29 ` Thomas Monjalon
2018-05-13 23:12 ` 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=fbfaf56b-40b1-f753-4520-993a0691baf8@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@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).