Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@linux.intel.com>
To: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
Cc: "Gote, Nitin R" <nitin.r.gote@intel.com>,
	Andi Shyti <andi.shyti@linux.intel.com>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	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>,
	"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: Thu, 12 Jun 2025 13:30:42 +0200	[thread overview]
Message-ID: <aEq6YquLee2oSt1i@ashyti-mobl2.lan> (raw)
In-Reply-To: <3881406.kQq0lBPeGt@jkrzyszt-mobl2.ger.corp.intel.com>

Hi Janusz,

On Thu, Jun 12, 2025 at 11:45:46AM +0200, Janusz Krzysztofik wrote:
> On Thursday, 12 June 2025 11:35:31 CEST Jani Nikula wrote:
> > On Thu, 12 Jun 2025, Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com> wrote:
> > > On Wednesday, 11 June 2025 22:54:40 CEST Andi Shyti wrote:
> > >> 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.
> > >
> > > I'm not sure.  I found no single word on the *subsystem* component of the 
> > > canonical patch format subject line (or commit message) expected to reflect 
> > > any directory structure in case of DRM.
> > 
> > It's not about the directory structure, though, but rather about
> > (admittedly unwritten) conventions. Usually about driver components,
> > features or platforms.
> > 
> > See:
> > 
> > $ git log --since={5years} --no-merges --pretty=%s -- "<PATH>" | sed 's/:.*//' | sort | uniq -c | sort -rn
> > 
> > Where "<PATH>" is drivers/gpu/drm/i915/gt/intel_ring_submission.c or
> > drivers/gpu/drm/i915/gt.
> > 
> > "ring" or "submission" is just not there in the prefix, at all.
> 
> I see.  Is there a convention for designating old, pre-execlists *platforms* 
> as affected subsystem / area?  Or is describing it in the summary phrase of 
> the commit message the only way?

it's an unwritten rule and my feeling is that these tings take
their own track without anyone deciding it officially.

Indeed every community has its own way of doing it. As you know
already, in i915 we have always used:

drm/i915:
drm/i915/gt:
drm/i915/gem:
drm/i915/gt/guc: (or drm/i915/guc:)
drm/i915/display:
...

pointing to the directory rather than the topic or the file.

In my opinion using "ring_submission:" is not wrong and it makes
sense, but it's out of the ordinary and this would be the only
patch doing it.

That's why this title is a little odd, unless we all agree to
change and set a convention.

Thanks,
Andi

  reply	other threads:[~2025-06-12 11:30 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
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 [this message]
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=aEq6YquLee2oSt1i@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