From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "Harrison, John C" <john.c.harrison@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [Intel-gfx 1/2] drm/i915/selftests: Use correct selfest calls for live tests
Date: Tue, 16 Aug 2022 01:54:52 +0000 [thread overview]
Message-ID: <bdc0d8ac2e84012fc72a0b892fba3c60421c19f2.camel@intel.com> (raw)
In-Reply-To: <442e7caa-054e-9c1c-7d02-4d0a5cad6244@intel.com>
Hmmm - i guess I've been it wrong all the while (been using the same script for a while).
Will fix - thanks
...alan
On Mon, 2022-08-15 at 15:40 -0700, Harrison, John C wrote:
> On 8/15/2022 09:01, Alan Previn wrote:
> > From: Matthew Brost <matthew.brost@intel.com>
> >
> > This will help in an upcoming patch where the live selftest wrappers
> > are extended to do more.
> >
> > Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> As per previous review, you still need to add your s-o-b as well as you
> are posting the patch.
>
> Also, why is the subject "[Intel-gfx X/2]" rather than "[PATCH X/2]"?
> The mailing list automatically adds the "[Intel-gfx]" prefix. You just
> need to use the standard "PATCH" or "PATCH v###" as appropriate.
>
> John.
>
next prev parent reply other threads:[~2022-08-16 1:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 16:01 [Intel-gfx] [Intel-gfx 0/2] Delay disabling scheduling on a context Alan Previn
2022-08-15 16:01 ` [Intel-gfx] [Intel-gfx 1/2] drm/i915/selftests: Use correct selfest calls for live tests Alan Previn
2022-08-15 22:40 ` John Harrison
2022-08-16 1:54 ` Teres Alexis, Alan Previn [this message]
2022-08-15 16:01 ` [Intel-gfx] [Intel-gfx 2/2] drm/i915/guc: Add delay to disable scheduling after pin count goes to zero Alan Previn
2022-08-15 23:57 ` John Harrison
2022-08-16 1:02 ` Teres Alexis, Alan Previn
2022-08-15 16:33 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Delay disabling scheduling on a context (rev4) Patchwork
2022-08-15 16:55 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2022-08-14 22:43 [Intel-gfx] [Intel-gfx 0/2] Delay disabling scheduling on a context Alan Previn
2022-08-14 22:43 ` [Intel-gfx] [Intel-gfx 1/2] drm/i915/selftests: Use correct selfest calls for live tests Alan Previn
2022-06-28 5:51 [Intel-gfx] [Intel-gfx 0/2] Delay disabling scheduling on a context Alan Previn
2022-06-28 5:51 ` [Intel-gfx] [Intel-gfx 1/2] drm/i915/selftests: Use correct selfest calls for live tests Alan Previn
2022-07-28 19:45 ` John Harrison
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=bdc0d8ac2e84012fc72a0b892fba3c60421c19f2.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=john.c.harrison@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