From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>,
Andi Shyti <andi.shyti@linux.intel.com>
Cc: Ville Syrjala <ville.syrjala@intel.com>,
intel-gfx@lists.freedesktop.org,
Lucas De Marchi <lucas.demarchi@intel.com>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH v3 1/4] drm/i915/display: remove drm_device aliases
Date: Tue, 11 Oct 2022 12:19:54 +0100 [thread overview]
Message-ID: <0f10a183-d86b-8ec7-8ce1-368c8bd25123@linux.intel.com> (raw)
In-Reply-To: <87h70ay8fr.fsf@intel.com>
On 11/10/2022 11:13, Jani Nikula wrote:
> On Tue, 11 Oct 2022, Andi Shyti <andi.shyti@linux.intel.com> wrote:
>> On Mon, Oct 10, 2022 at 04:31:28PM +0200, Andi Shyti wrote:
>>> On Thu, Oct 06, 2022 at 10:48:44PM +0200, Andrzej Hajda wrote:
>>>> drm_device pointers are unwelcome.
>>>>
>>>> Signed-off-by: Andrzej Hajda <andrzej.hajda@intel.com>
>>>
>>> Acked-by: Andi Shyti <andi.shyti@linux.intel.com>
>>
>> Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
>>
>> Only this first patch is strictly related to display, I'm taking
>> the series in intel-gt-next. Anyone against?
>
> Absolutely against. That logic is backwards.
>
> drm-intel-gt-next is for stuff that's strictly about gt/gem. Everything
> else, especially stuff touching common code, needs to go through
> drm-intel-next.
>
> There's nothing here that's gt/gem specific.
Glanced over the series and although there are a few bits which are not
about display, it does seem majority is either display or common code so
I agree it should all go in via drm-intel-next.
Regards,
Tvrtko
next prev parent reply other threads:[~2022-10-11 11:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 16:31 [Intel-gfx] [PATCH v2 0/4] Simplify uncore register updates Andrzej Hajda
2022-10-06 16:31 ` [Intel-gfx] [PATCH v2 1/4] drm/i915/display: Use drm_device alias if defined Andrzej Hajda
2022-10-06 16:41 ` Ville Syrjälä
2022-10-06 20:48 ` [Intel-gfx] [PATCH v3 1/4] drm/i915/display: remove drm_device aliases Andrzej Hajda
2022-10-10 14:31 ` Andi Shyti
2022-10-10 15:22 ` Jani Nikula
2022-10-11 10:09 ` Andi Shyti
2022-10-11 10:13 ` Jani Nikula
2022-10-11 10:17 ` Jani Nikula
2022-10-11 10:28 ` Andi Shyti
2022-10-11 11:19 ` Tvrtko Ursulin [this message]
2022-10-06 16:31 ` [Intel-gfx] [PATCH v2 2/4] drm/i915/display: Use intel_uncore alias if defined Andrzej Hajda
2022-10-06 16:31 ` [Intel-gfx] [PATCH v2 3/4] drm/i915: make intel_uncore_rmw() write unconditionally Andrzej Hajda
2022-10-06 16:32 ` [Intel-gfx] [PATCH v2 4/4] drm/i915: use proper helper for register updates Andrzej Hajda
2022-10-14 17:57 ` Matt Roper
2022-10-17 9:28 ` Andrzej Hajda
2022-10-06 16:51 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Simplify uncore register updates (rev2) Patchwork
2022-10-06 17:16 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-10-06 21:26 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Simplify uncore register updates (rev3) Patchwork
2022-10-06 21:47 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-10-07 5:00 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for Simplify uncore register updates (rev2) Patchwork
2022-10-11 22:18 ` [Intel-gfx] [PATCH v2 0/4] Simplify uncore register updates Andi Shyti
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=0f10a183-d86b-8ec7-8ce1-368c8bd25123@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=andrzej.hajda@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=ville.syrjala@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