From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/pxp: Optimize GET_PARAM:PXP_STATUS
Date: Fri, 2 Jun 2023 15:32:50 +0000 [thread overview]
Message-ID: <ce544e21da67306a406920f5cd72504619ffbe3f.camel@intel.com> (raw)
In-Reply-To: <87y1l2dnjt.fsf@intel.com>
Thanks Jani - will rev this up and fix these.
On Fri, 2023-06-02 at 16:03 +0300, Jani Nikula wrote:
> On Thu, 01 Jun 2023, Alan Previn <alan.previn.teres.alexis@intel.com> wrote:
> > After recent discussions with Mesa folks, it was requested
> > that we optimize i915's GET_PARAM for the PXP_STATUS without
> > changing the UAPI spec.
> >
> > This patch adds this additional optimizations:
>
> Nitpick, please avoid "This patch". It's redundant, and after the patch
> gets applied it becomes a commit, not a patch.
>
> Instead, use the imperative mood, e.g. "Add these additional
> optimizations".
>
> See https://docs.kernel.org/process/submitting-patches.html#describe-your-changes
alan:snip
>
> > -int intel_pxp_get_readiness_status(struct intel_pxp *pxp)
> > +int intel_pxp_get_readiness_status(struct intel_pxp *pxp, int timeout)
>
> It would help the reader if you named the parameter timeout_ms. Assuming
> the unit is ms.
alan:snip
> > -is_fw_err_platform_config(u32 type)
> > +is_fw_err_platform_config(u32 type, struct intel_pxp *pxp)
>
> It's customary to have the parameters ordered from higher context to
> lower.
>
alan:snip
next prev parent reply other threads:[~2023-06-02 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 17:45 [Intel-gfx] [PATCH] drm/i915/pxp: Optimize GET_PARAM:PXP_STATUS Alan Previn
2023-06-01 23:10 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-06-02 13:03 ` [Intel-gfx] [PATCH] " Jani Nikula
2023-06-02 15:32 ` Teres Alexis, Alan Previn [this message]
2023-06-20 14:30 ` Balasubrawmanian, Vivaik
2023-06-29 22:39 ` Teres Alexis, Alan Previn
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=ce544e21da67306a406920f5cd72504619ffbe3f.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.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