From: "Winkler, Tomas" <tomas.winkler@intel.com>
To: Pavel Machek <pavel@ucw.cz>,
kernel list <linux-kernel@vger.kernel.org>,
"Lubart, Vitaly" <vitaly.lubart@intel.com>,
"Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>,
"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>,
"joonas.lahtinen@linux.intel.com"
<joonas.lahtinen@linux.intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>,
"masahiroy@kernel.org" <masahiroy@kernel.org>
Subject: RE: intel_mei_pxp: needs better help text
Date: Sun, 17 Oct 2021 12:45:50 +0000 [thread overview]
Message-ID: <dc2ae3d0c3e6452b80a53ca6ca2b20b8@intel.com> (raw)
In-Reply-To: <20211017072356.GA4756@duo.ucw.cz>
Thank you, we will handle that.
Please mind our weekend.
Thanks
Tomas
> -----Original Message-----
> From: Pavel Machek <pavel@ucw.cz>
> Sent: Sunday, October 17, 2021 10:24
> To: kernel list <linux-kernel@vger.kernel.org>; Lubart, Vitaly
> <vitaly.lubart@intel.com>; Winkler, Tomas <tomas.winkler@intel.com>;
> Ceraolo Spurio, Daniele <daniele.ceraolospurio@intel.com>;
> jani.nikula@linux.intel.com; joonas.lahtinen@linux.intel.com; Vivi, Rodrigo
> <rodrigo.vivi@intel.com>; intel-gfx@lists.freedesktop.org; linux-
> kbuild@vger.kernel.org; masahiroy@kernel.org
> Subject: Re: intel_mei_pxp: needs better help text
>
> Hi!
>
> Extended Cc list. Should I attempt to prepare a patch?
>
> Best regards,
> Pavel
>
> On Thu 2021-10-14 12:53:34, Pavel Machek wrote:
> >
> > CONFIG_INTEL_MEI_PXP:
> >
> > MEI Support for PXP Services on Intel platforms.
> >
> > Enables the ME FW services required for PXP support through
> > I915 display driver of Intel.
> >
> >
> > That's ... very useless help text. According to
> > https://www.phoronix.com/scan.php?page=news_item&px=Intel-PXP-
> Protecte
> > d-Xe-Path this is some kind of DRM. Help text should probably say it
> > has to do with i915 video, and explain the acronyms, and probably its
> > usecases.
> >
> >
> >
> > --
> > http://www.livejournal.com/~pavelmachek
>
>
>
> --
> http://www.livejournal.com/~pavelmachek
prev parent reply other threads:[~2021-10-17 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 10:53 intel_mei_pxp: needs better help text Pavel Machek
2021-10-17 7:23 ` Pavel Machek
2021-10-17 12:45 ` Winkler, Tomas [this message]
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=dc2ae3d0c3e6452b80a53ca6ca2b20b8@intel.com \
--to=tomas.winkler@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=pavel@ucw.cz \
--cc=rodrigo.vivi@intel.com \
--cc=vitaly.lubart@intel.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