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 v2 1/1] drm/i915/pxp: Use drm_dbg if arb session failed due to fw version
Date: Wed, 21 Dec 2022 17:33:24 +0000 [thread overview]
Message-ID: <74a4e4f38be56de1c3810e5a3dbe03fb3ec0939b.camel@intel.com> (raw)
In-Reply-To: <87zgbh12hf.fsf@intel.com>
On Wed, 2022-12-21 at 12:21 +0200, Jani Nikula wrote:
> On Tue, 20 Dec 2022, Alan Previn <alan.previn.teres.alexis@intel.com> wrote:
> >
Alan:[snip]
> > +++ b/drivers/gpu/drm/i915/pxp/intel_pxp_tee.c
> > @@ -298,6 +298,11 @@ int intel_pxp_tee_cmd_create_arb_session(struct intel_pxp *pxp,
> >
> > if (ret)
> > drm_err(&i915->drm, "Failed to send tee msg ret=[%d]\n", ret);
> > +
>
> Superfluous newline that someone's gonna send a patch later to
> remove. Easier to just not add it.
>
> BR,
> Jani.
>
Alan: will fix
next prev parent reply other threads:[~2022-12-21 17:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 22:11 [Intel-gfx] [PATCH v2 1/1] drm/i915/pxp: Use drm_dbg if arb session failed due to fw version Alan Previn
2022-12-20 22:11 ` Alan Previn
2022-12-21 10:21 ` [Intel-gfx] " Jani Nikula
2022-12-21 17:33 ` Teres Alexis, Alan Previn [this message]
2022-12-21 17:49 ` [Intel-gfx] [PATCH v3 " Alan Previn
2022-12-21 17:49 ` Alan Previn
2023-01-12 3:19 ` [Intel-gfx] " Belgaumkar, Vinay
2022-12-22 9:56 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [v3,1/1] drm/i915/pxp: Use drm_dbg if arb session failed due to fw version (rev2) Patchwork
2022-12-22 15:52 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=74a4e4f38be56de1c3810e5a3dbe03fb3ec0939b.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 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.