Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: Nirmoy Das <nirmoy.das@intel.com>
Subject: Re: [Intel-gfx] [PATCH 1/7] drm/i915: add i915_config.h and move relevant declarations there
Date: Fri, 20 Jan 2023 10:22:01 +0200	[thread overview]
Message-ID: <875yd1aa52.fsf@intel.com> (raw)
In-Reply-To: <c0200ae2-8e53-c439-0417-7f682c15da0e@linux.intel.com>

On Wed, 18 Jan 2023, Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> wrote:
> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

Thanks for the reviews and acks, pushed to drm-intel-next.

Despite having a lot of gem/gt stuff, I opted to use drm-intel-next
instead of drm-intel-gt-next, because I think the i915_drv.h changes
belong in din, and it's easier to sync din -> dign than vice versa.

BR,
Jani.

>
> It however made me spot the wasteful out of line call to 
> i915_fence_context_timeout, with even u64 used as plain bool, so I might 
> be tempted to do something about that as a follow up.
>
> Regards,
>
> Tvrtko

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2023-01-20  8:22 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18 13:15 [Intel-gfx] [PATCH 1/7] drm/i915: add i915_config.h and move relevant declarations there Jani Nikula
2023-01-18 13:15 ` [Intel-gfx] [PATCH 2/7] drm/i915: move I915_IDLE_ENGINES_TIMEOUT next to its only user Jani Nikula
2023-01-18 13:27   ` Tvrtko Ursulin
2023-01-20 10:32   ` Rodrigo Vivi
2023-01-20 10:39     ` Jani Nikula
2023-01-18 13:15 ` [Intel-gfx] [PATCH 3/7] drm/i915: drop a number of unnecessary forward declarations Jani Nikula
2023-01-18 13:28   ` Tvrtko Ursulin
2023-01-20 10:34   ` Rodrigo Vivi
2023-01-18 13:15 ` [Intel-gfx] [PATCH 4/7] drm/i915: move a few HAS_ macros closer to their place Jani Nikula
2023-01-20 10:36   ` Rodrigo Vivi
2023-01-18 13:15 ` [Intel-gfx] [PATCH 5/7] drm/i915: move I915_GEM_GPU_DOMAINS to i915_gem.h Jani Nikula
2023-01-18 13:27   ` Tvrtko Ursulin
2023-01-18 14:05   ` Das, Nirmoy
2023-01-20 10:40   ` Rodrigo Vivi
2023-01-18 13:15 ` [Intel-gfx] [PATCH 6/7] drm/i915: move I915_COLOR_UNEVICTABLE to i915_gem_gtt.h Jani Nikula
2023-01-18 13:28   ` Tvrtko Ursulin
2023-01-20 10:43   ` Rodrigo Vivi
2023-01-23 13:17     ` Jani Nikula
2023-01-18 13:15 ` [Intel-gfx] [PATCH 7/7] drm/i915: move GT_FREQUENCY_MULTIPLIER and GEN9_FREQ_SCALER to intel_rps.h Jani Nikula
2023-01-18 13:28   ` Tvrtko Ursulin
2023-01-18 13:32 ` [Intel-gfx] [PATCH 1/7] drm/i915: add i915_config.h and move relevant declarations there Tvrtko Ursulin
2023-01-20  8:22   ` Jani Nikula [this message]
2023-01-18 22:03 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/7] " Patchwork
2023-01-18 22:34 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-01-19  1:39 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/7] drm/i915: add i915_config.h and move relevant declarations there (rev2) Patchwork
2023-01-19  1:39 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-01-19  2:09 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-01-20  1:16 ` [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=875yd1aa52.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=nirmoy.das@intel.com \
    --cc=tvrtko.ursulin@linux.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