From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Mathias Krause <minipli@grsecurity.net>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 2/2] drm/i915: Clarify type evolution of uabi_node/uabi_engines
Date: Wed, 4 Oct 2023 11:44:25 +0100 [thread overview]
Message-ID: <24d32a0f-6d04-e892-26c4-ade9546d7bc6@linux.intel.com> (raw)
In-Reply-To: <d174ff90-4ddc-f256-d1ae-c673a64926b7@grsecurity.net>
On 04/10/2023 10:52, Mathias Krause wrote:
> On 03.10.23 09:32, Tvrtko Ursulin wrote:
>> On 29/09/2023 12:00, Tvrtko Ursulin wrote:
>>> [...]
>>> Thanks again!
>>>
>>> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> Patches pushed to drm-intel-gt-next.
>>
>
> Thanks, Tvrtko!
>
> I guess this implies no backport of the first patch to older kernels, as
> it affects v6.3+?
It will land in 6.6+ from purely drm and drm-intel flows but indeed, we
forgot about the stable tag.
I am however pretty sure it will get picked up nevertheless, since the
Fixes: tag is correct, and I think stable maintainers use it from their
scripts to identify interesting patches.
Regards,
Tvrtko
next prev parent reply other threads:[~2023-10-04 10:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 18:20 [Intel-gfx] [PATCH v2 0/2] drm/i915: fix rb-tree/llist/list confusion Mathias Krause
2023-09-28 18:20 ` [Intel-gfx] [PATCH v2 1/2] drm/i915: Register engines early to avoid type confusion Mathias Krause
2023-09-29 10:57 ` Tvrtko Ursulin
2023-09-28 18:20 ` [Intel-gfx] [PATCH v2 2/2] drm/i915: Clarify type evolution of uabi_node/uabi_engines Mathias Krause
2023-09-29 11:00 ` Tvrtko Ursulin
2023-10-03 7:32 ` Tvrtko Ursulin
2023-10-04 9:52 ` Mathias Krause
2023-10-04 10:44 ` Tvrtko Ursulin [this message]
2023-09-28 19:29 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: fix rb-tree/llist/list confusion (rev2) Patchwork
2023-09-28 19:29 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-09-28 19:48 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-09-29 7:55 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: fix rb-tree/llist/list confusion (rev3) Patchwork
2023-09-29 7:55 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-09-29 8:07 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-09-29 12:39 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-10-02 19:02 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: fix rb-tree/llist/list confusion (rev4) Patchwork
2023-10-02 19:02 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-10-02 19:12 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-10-02 20:42 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=24d32a0f-6d04-e892-26c4-ade9546d7bc6@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=minipli@grsecurity.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