Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Maxime Ripard <mripard@kernel.org>
Cc: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>,
	dri-devel@lists.freedesktop.org,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	amd-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	intel-gfx@lists.freedesktop.org, linux-media@vger.kernel.org,
	linaro-mm-sig@lists.linaro.org, kernel-dev@igalia.com
Subject: Re: [PATCH v4 2/9] dma-fence: Use a flag for 64-bit seqnos
Date: Tue, 3 Jun 2025 18:10:41 +0200	[thread overview]
Message-ID: <45240bbc-5b64-4e55-85c8-d8abb16abcfa@amd.com> (raw)
In-Reply-To: <20250603-outrageous-kakapo-of-felicity-6dc41a@houat>

On 6/3/25 15:13, Maxime Ripard wrote:
> Hi,
> 
> On Mon, Jun 02, 2025 at 04:42:27PM +0200, Christian König wrote:
>> On 6/2/25 15:05, Tvrtko Ursulin wrote:
>>> On 15/05/2025 14:15, Christian König wrote:
>>>> Hey drm-misc maintainers,
>>>>
>>>> can you guys please backmerge drm-next into drm-misc-next?
>>>>
>>>> I want to push this patch here but it depends on changes which are partially in drm-next and partially in drm-misc-next.
>>>
>>> Looks like the backmerge is still pending?
>>
>> Yes, @Maarten, @Maxime and @Thomas ping on this.
> 
> It's done

Thanks, I will start merge things tomorrow.

Regards,
Christian.

> 
> Maxime


  parent reply	other threads:[~2025-06-03 16:10 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-15  9:49 [PATCH v4 0/9] Some (drm_sched_|dma_)fence lifetime issues Tvrtko Ursulin
2025-05-15  9:49 ` [PATCH v4 1/9] dma-fence: Change signature of __dma_fence_is_later Tvrtko Ursulin
2025-05-15  9:49 ` [PATCH v4 2/9] dma-fence: Use a flag for 64-bit seqnos Tvrtko Ursulin
2025-05-15 13:15   ` Christian König
2025-06-02 13:05     ` Tvrtko Ursulin
2025-06-02 14:42       ` Christian König
2025-06-02 15:25         ` Tvrtko Ursulin
     [not found]           ` <2ffc513c-2d11-4b76-b9c9-c7cb7841e386@amd.com>
2025-06-03 11:30             ` Tvrtko Ursulin
2025-06-03 12:40               ` Christian König
2025-06-03 12:48                 ` Tvrtko Ursulin
2025-06-03 14:00                   ` Christian König
2025-06-03 13:13         ` Maxime Ripard
2025-06-03 15:00           ` Tvrtko Ursulin
2025-06-03 16:27             ` Christian König
2025-06-03 16:53               ` Tvrtko Ursulin
2025-06-03 16:10           ` Christian König [this message]
2025-05-15  9:49 ` [PATCH v4 3/9] dma-fence: Add helpers for accessing driver and timeline name Tvrtko Ursulin
2025-05-15  9:49 ` [PATCH v4 4/9] sync_file: Use dma-fence driver and timeline name helpers Tvrtko Ursulin
2025-05-15  9:50 ` [PATCH v4 5/9] drm/i915: " Tvrtko Ursulin
2025-05-15 14:46   ` Andi Shyti
2025-05-15  9:50 ` [PATCH v4 6/9] dma-fence: Add safe access helpers and document the rules Tvrtko Ursulin
2025-05-15  9:50 ` [PATCH v4 7/9] sync_file: Protect access to driver and timeline name Tvrtko Ursulin
2025-05-15  9:50 ` [PATCH v4 8/9] drm/i915: " Tvrtko Ursulin
2025-05-15 15:08   ` Andi Shyti
2025-05-15  9:50 ` [PATCH v4 9/9] drm/xe: Make dma-fences compliant with the safe access rules Tvrtko Ursulin
2025-05-15 10:47 ` ✓ CI.Patch_applied: success for Some (drm_sched_|dma_)fence lifetime issues (rev3) Patchwork
2025-05-15 10:48 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-15 10:49 ` ✓ CI.KUnit: success " Patchwork
2025-05-15 10:59 ` ✓ CI.Build: " Patchwork
2025-05-15 11:02 ` ✓ CI.Hooks: " Patchwork
2025-05-15 11:03 ` ✗ CI.checksparse: warning " Patchwork
2025-05-15 11:27 ` ✓ Xe.CI.BAT: success " Patchwork
2025-05-15 20:53 ` ✗ Xe.CI.Full: failure " Patchwork
2025-05-27  2:02 ` ✗ CI.Patch_applied: " 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=45240bbc-5b64-4e55-85c8-d8abb16abcfa@amd.com \
    --to=christian.koenig@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=kernel-dev@igalia.com \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-media@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=tvrtko.ursulin@igalia.com \
    --cc=tzimmermann@suse.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