From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: jspewock@iol.unh.edu, probb@iol.unh.edu,
Honnappa.Nagarahalli@arm.com, npratte@iol.unh.edu,
wathsala.vithanage@arm.com, yoan.picchi@foss.arm.com,
thomas@monjalon.net, paul.szczepanek@arm.com,
Luca.Vizzarro@arm.com, alex.chapman@arm.com
Cc: dev@dpdk.org
Subject: Re: [PATCH v1 0/1] dts: fix hugepage mounting
Date: Mon, 9 Sep 2024 10:23:53 +0200 [thread overview]
Message-ID: <a897bc4d-640c-4549-ad17-ce0724480281@pantheon.tech> (raw)
In-Reply-To: <20240812150421.31226-1-jspewock@iol.unh.edu>
Reviewed-by: Juraj Linkeš <juraj.linkes@pantheon.tech>
On 12. 8. 2024 17:04, jspewock@iol.unh.edu wrote:
> From: Jeremy Spewock <jspewock@iol.unh.edu>
>
> Currently in the DTS framework there are some commands used for
> remounting hugepages that require super-user privileges but do not use
> them, causing them to throw errors whenever they are run as a non-root
> user. This patches fixes these problems by simply adding a flag that
> enables admin privileges for the commands that are missing them.
>
> Jeremy Spewock (1):
> dts: add admin privileges to hugepage mounting
>
> dts/framework/testbed_model/linux_session.py | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
next prev parent reply other threads:[~2024-09-09 8:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 15:04 [PATCH v1 0/1] dts: fix hugepage mounting jspewock
2024-08-12 15:04 ` [PATCH v1 1/1] dts: add admin privileges to " jspewock
2024-08-12 15:17 ` Nicholas Pratte
2024-09-09 15:44 ` Luca Vizzarro
2024-09-09 15:48 ` Juraj Linkeš
2024-09-09 8:23 ` Juraj Linkeš [this message]
2024-09-09 15:52 ` [PATCH v1 0/1] dts: fix " Juraj Linkeš
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=a897bc4d-640c-4549-ad17-ce0724480281@pantheon.tech \
--to=juraj.linkes@pantheon.tech \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Luca.Vizzarro@arm.com \
--cc=alex.chapman@arm.com \
--cc=dev@dpdk.org \
--cc=jspewock@iol.unh.edu \
--cc=npratte@iol.unh.edu \
--cc=paul.szczepanek@arm.com \
--cc=probb@iol.unh.edu \
--cc=thomas@monjalon.net \
--cc=wathsala.vithanage@arm.com \
--cc=yoan.picchi@foss.arm.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.