From: Andi Shyti <andi.shyti@linux.intel.com>
To: "Gote, Nitin R" <nitin.r.gote@intel.com>
Cc: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
Tvrtko Ursulin <tursulin@ursulin.net>,
Chris Wilson <chris.p.wilson@linux.intel.com>,
"Auld, Matthew" <matthew.auld@intel.com>,
Andi Shyti <andi.shyti@linux.intel.com>,
"Brzezinka, Sebastian" <sebastian.brzezinka@intel.com>,
"Niemiec, Krzysztof" <krzysztof.niemiec@intel.com>,
"Karas, Krzysztof" <krzysztof.karas@intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/ring_submission: Fix timeline left held on VMA alloc error
Date: Wed, 11 Jun 2025 22:54:40 +0200 [thread overview]
Message-ID: <aEntEHqvZ10SaE8u@ashyti-mobl2.lan> (raw)
In-Reply-To: <IA3PR11MB89873936B6D887A59ABD909CD075A@IA3PR11MB8987.namprd11.prod.outlook.com>
Hi Nitin,
On Wed, Jun 11, 2025 at 03:45:30PM +0000, Gote, Nitin R wrote:
> [...]
> > Subject: [PATCH] drm/i915/ring_submission: Fix timeline left held on VMA alloc
> > error
> >
>
> Generally, it's preferred to use "drm/i915/gt:" file path over "drm/i915/ring_submission:" file name in the commit title.
good observation, I missed it. I agree with Nitin on this, it can
be fixed before merging.
Andi
next prev parent reply other threads:[~2025-06-11 20:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 10:42 [PATCH] drm/i915/ring_submission: Fix timeline left held on VMA alloc error Janusz Krzysztofik
2025-06-11 11:17 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/ring_submission: Fix timeline left held on VMA alloc error (rev2) Patchwork
2025-06-11 11:43 ` ✓ i915.CI.BAT: success " Patchwork
2025-06-11 13:39 ` ✓ i915.CI.Full: " Patchwork
2025-06-11 15:45 ` [PATCH] drm/i915/ring_submission: Fix timeline left held on VMA alloc error Gote, Nitin R
2025-06-11 20:54 ` Andi Shyti [this message]
2025-06-12 9:08 ` Janusz Krzysztofik
2025-06-12 9:35 ` Jani Nikula
2025-06-12 9:45 ` Janusz Krzysztofik
2025-06-12 11:30 ` Andi Shyti
2025-06-12 11:46 ` Janusz Krzysztofik
2025-06-11 20:53 ` Andi Shyti
2025-06-30 13:46 ` Andi Shyti
-- strict thread matches above, loose matches on Subject: below --
2025-06-06 13:58 Janusz Krzysztofik
2025-06-10 13:59 ` Sebastian Brzezinka
2025-06-10 14:06 ` Krzysztof Niemiec
2025-06-11 8:03 ` Krzysztof Karas
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=aEntEHqvZ10SaE8u@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=chris.p.wilson@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=janusz.krzysztofik@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=krzysztof.karas@intel.com \
--cc=krzysztof.niemiec@intel.com \
--cc=matthew.auld@intel.com \
--cc=nitin.r.gote@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=sebastian.brzezinka@intel.com \
--cc=tursulin@ursulin.net \
/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