From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "dan.carpenter@linaro.org" <dan.carpenter@linaro.org>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"airlied@gmail.com" <airlied@gmail.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gsc: Fix error code in intel_gsc_uc_heci_cmd_submit_nonpriv()
Date: Thu, 8 Jun 2023 18:49:37 +0000 [thread overview]
Message-ID: <50925f9f08257a00fb21ffec413f0dbe14819a0a.camel@intel.com> (raw)
In-Reply-To: <2cf8065f-6841-442e-b68c-14e0d2b055c8@kadam.mountain>
On Thu, 2023-06-08 at 11:37 +0300, Dan Carpenter wrote:
> On Wed, Jun 07, 2023 at 06:44:54PM +0000, Teres Alexis, Alan Previn wrote:
> > On Tue, 2023-06-06 at 21:32 +0300, Dan Carpenter wrote:
> > > On Tue, Jun 06, 2023 at 06:07:19PM +0000, Teres Alexis, Alan Previn wrote:
> > > > That was my bad, i could have sword i'd fixed that before the final rev. Thanks for fixing this.
> > > > nit: below function applies to MTL only which at the moment is still force-probed, so not sure if the fixes tag is significant.
> > > >
> > >
> > > The Fixes tag is correct. It's definitely a bug fix.
> > >
> > > (I invented the Fixes tag so technically that makes me the worlds #1
> > > expert on Fixes tags).
> > >
> > So sorry my bad.
>
> LOL.
>
> Presumably the appology was intended sarcastically? Hopefully? Oh my
> goodness. ROFL...
>
lol - i'll take the 5th here - i should have phrased it differrently - my bad.
next prev parent reply other threads:[~2023-06-08 18:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 8:22 [Intel-gfx] [PATCH] drm/i915/gsc: Fix error code in intel_gsc_uc_heci_cmd_submit_nonpriv() Dan Carpenter
2023-06-06 9:18 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-06-06 18:07 ` [Intel-gfx] [PATCH] " Teres Alexis, Alan Previn
2023-06-06 18:32 ` Dan Carpenter
2023-06-07 18:44 ` Teres Alexis, Alan Previn
2023-06-08 8:37 ` Dan Carpenter
2023-06-08 18:49 ` Teres Alexis, Alan Previn [this message]
2023-06-07 0:39 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " Patchwork
2023-06-08 0:10 ` [Intel-gfx] [PATCH] " Andi Shyti
2023-06-08 0:14 ` Andi Shyti
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=50925f9f08257a00fb21ffec413f0dbe14819a0a.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=airlied@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=rodrigo.vivi@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