public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@linux.intel.com>
To: Karolina Drobnik <karolina.drobnik@intel.com>
Cc: Thomas Voegtle <tv@lio96.de>,
	intel-gfx@lists.freedesktop.org, chris.p.wilson@intel.com,
	Chris Wilson <chris@chris-wilson.co.uk>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH 1/3] drm/i915/gem: Look for waitboosting across the whole object prior to individual waits
Date: Fri, 8 Jul 2022 13:38:08 +0200	[thread overview]
Message-ID: <YsgXIE6Vg+7BuFKS@alfio.lan> (raw)
In-Reply-To: <d2601b7a-247f-4638-1068-92fa8f35ef58@intel.com>

Hi Karolina,

[...]

> > > > +	dma_resv_for_each_fence_unlocked(&cursor, fence) {
> > > > +		if (dma_fence_is_i915(fence) &&
> > > > +		    !i915_request_started(to_request(fence)))
> > > > +			intel_rps_boost(to_request(fence));
> > > > +	}
> > 
> > you can remove the brackets here.
> > 
> > Andi
> 
> Would you like me to send v2 for it?

if the committer takes care of removing it, then no need,
otherwise, please yes, resend it. Even if it's a stupid nitpick,
if it gets applied it would be very difficult to get it fixed[*].

Didn't checkpatch.pl complain about it?

If you are going to resend it, you can add my:

Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>

also here.

Thanks,
Andi

[*] Because just minor coding style patches are generally
rejected, the only way for fixing style issues would be if:

 1. someone is working in that part of the code
 2. someone will sneak in the code fix in some unrelated patch 
    screwing up git blame
 3. someone will send a big series on this file and have some
    trivial coding style patches in it.

Amongst the three above, number '2' is the one I dislike the
most, but unfortunately that's also the most used.

  reply	other threads:[~2022-07-08 11:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-05 10:57 [Intel-gfx] [PATCH 0/3] drm/i915: Apply waitboosting before fence wait Karolina Drobnik
2022-07-05 10:57 ` [Intel-gfx] [PATCH 1/3] drm/i915/gem: Look for waitboosting across the whole object prior to individual waits Karolina Drobnik
2022-07-07 17:57   ` Rodrigo Vivi
2022-07-07 21:50     ` Andi Shyti
2022-07-08 10:15       ` Karolina Drobnik
2022-07-08 11:38         ` Andi Shyti [this message]
2022-07-08 14:14           ` Karolina Drobnik
2022-07-05 10:57 ` [Intel-gfx] [PATCH 2/3] drm/i915: Bump GT idling delay to 2 jiffies Karolina Drobnik
2022-07-07 18:09   ` Rodrigo Vivi
2022-07-07 21:52   ` Andi Shyti
2022-07-05 10:57 ` [Intel-gfx] [PATCH 3/3] drm/i915/gt: Only kick the signal worker if there's been an update Karolina Drobnik
2022-07-05 13:51 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Apply waitboosting before fence wait Patchwork
2022-07-05 14:10 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-07-05 16: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=YsgXIE6Vg+7BuFKS@alfio.lan \
    --to=andi.shyti@linux.intel.com \
    --cc=chris.p.wilson@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=karolina.drobnik@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=tv@lio96.de \
    /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