From: Thomas Monjalon <thomas@monjalon.net>
To: Sarosh Arif <sarosh.arif@emumba.com>
Cc: dev@dpdk.org, john.mcnamara@intel.com, sthemmin@microsoft.com,
jerinj@marvell.com, mczekaj@marvell.com,
marko.kovacevic@intel.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] doc: fix references to /dev/huge
Date: Sun, 05 Jul 2020 22:44:29 +0200 [thread overview]
Message-ID: <159400495.1GMdgr3TlT@thomas> (raw)
In-Reply-To: <20200623055559.19068-1-sarosh.arif@emumba.com>
23/06/2020 07:55, Sarosh Arif:
> change /dev/huge to /dev/hugepages
>
> Bugzilla ID: 492
> Signed-off-by: Sarosh Arif <sarosh.arif@emumba.com>
Please could you explain why /dev/hugepages must be used,
in the commit log for the record?
FYI, a similar change was done in the website by Stephen.
next prev parent reply other threads:[~2020-07-05 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 5:55 [dpdk-dev] [PATCH] doc: fix references to /dev/huge Sarosh Arif
2020-07-05 20:44 ` Thomas Monjalon [this message]
2020-07-06 8:01 ` [dpdk-dev] [dpdk-stable] " Sarosh Arif
2020-07-30 23:31 ` Thomas Monjalon
2020-07-28 10:17 ` Burakov, Anatoly
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=159400495.1GMdgr3TlT@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=mczekaj@marvell.com \
--cc=sarosh.arif@emumba.com \
--cc=stable@dpdk.org \
--cc=sthemmin@microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.