From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <jbeulich@suse.com>, Juergen Gross <jgross@suse.com>
Cc: linux@weissschuh.net, Stefano Stabellini <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xen/privcmd: make option visible in Kconfig
Date: Wed, 17 Nov 2021 11:05:10 -0500 [thread overview]
Message-ID: <cb342108-c470-7623-0255-c4d35e2fa73d@oracle.com> (raw)
In-Reply-To: <f6957992-3431-c576-a8d4-daf4e60832cb@oracle.com>
On 11/16/21 5:33 PM, Boris Ostrovsky wrote:
>
> On 11/16/21 11:05 AM, Jan Beulich wrote:
>> On 16.11.2021 16:01, Juergen Gross wrote:
>>> On 16.11.21 15:55, Jan Beulich wrote:
>>>> On 16.11.2021 15:33, Juergen Gross wrote:
>>>>
>>>>> config XEN_PRIVCMD
>>>>> - tristate
>>>>> + tristate "Xen hypercall passthrough driver"
>>>>> depends on XEN
>>>>> default m
>>>>> + help
>>>>> + The hypercall passthrough driver allows user land programs to perform
>>>> Maybe worth adding "privileged" here? Albeit of course that's different
>>>> from the use of the word ...
>>> I guess you mean "... allows privileged user programs ..." (another
>>> variant might be "The privileged hypercall passthrough ...")?
>> The former, yes.
>
>
> I can apply with this change, no need to resend.
>
>
Applied to for-linus-5.16c
-boris
next prev parent reply other threads:[~2021-11-17 16:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 14:33 Juergen Gross
2021-11-16 14:55 ` Jan Beulich
2021-11-16 15:01 ` Juergen Gross
2021-11-16 16:05 ` Jan Beulich
2021-11-16 22:33 ` Boris Ostrovsky
2021-11-17 16:05 ` Boris Ostrovsky [this message]
2021-11-16 14:59 ` Thomas Weißschuh
-- strict thread matches above, loose matches on Subject: below --
2021-11-13 8:38 Thomas Weißschuh
2021-11-15 10:02 ` Jan Beulich
2021-11-15 10:25 ` Thomas Weißschuh
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=cb342108-c470-7623-0255-c4d35e2fa73d@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®