mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Almeida <daniel.almeida@collabora.com>
To: "Onur Özkan" <work@onurozkan.dev>
Cc: linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
	dri-devel@lists.freedesktop.org, dakr@kernel.org,
	aliceryhl@google.com, airlied@gmail.com, simona@ffwll.ch,
	ojeda@kernel.org, boqun@kernel.org, gary@garyguo.net,
	bjorn3_gh@protonmail.com, lossin@kernel.org,
	a.hindborg@kernel.org, tmgross@umich.edu
Subject: Re: [PATCH v7 0/3] drm/tyr: GPU reset infrastructure
Date: Wed, 11 Nov 2026 12:33:47 -0300	[thread overview]
Message-ID: <AE29D511-8F4A-49A3-BE4E-31E6411816D7@collabora.com> (raw)
In-Reply-To: <20261111100745.3929894-1-work@onurozkan.dev>

Hi Onur,

> 
> Any updates on this? I am preparing v2 of the GPU unplug series [1] which
> depends on this series. The reset patches need rebasing against current
> drm-rust-next.
> 
> Would you prefer me to send a rebased v8 and base unplug v2 on it or are
> you planning to pick up v7 and handle the rebase?
> 
> Thanks,
> Onur
> 
> [1]: https://lore.kernel.org/all/20260823-tyr-gpu-unplug-b4-v1-0-e99c07d4c785@onurozkan.dev
> 

I'm only waiting Alice's R-b before bringing this in. Feel free to send a
rebased version, since it will probably be needed for the unplug work too.

-- Daniel

  reply	other threads:[~2026-11-11 15:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-12 10:38 Onur Özkan
2026-09-12 10:39 ` Onur Özkan
2026-09-12 10:39 ` [PATCH v7 1/3] drm/tyr: clear stale IRQ state before soft reset Onur Özkan
2026-09-12 10:39 ` [PATCH v7 2/3] drm/tyr: add GPU reset infrastructure Onur Özkan
2026-09-12 10:39 ` [PATCH v7 3/3] drm/tyr: put iomem behind the hardware gate Onur Özkan
2026-09-23 13:55   ` Daniel Almeida
2026-09-23 13:56 ` [PATCH v7 0/3] drm/tyr: GPU reset infrastructure Daniel Almeida
2026-11-11 10:07   ` Onur Özkan
2026-11-11 15:33     ` Daniel Almeida [this message]
2026-11-12 14:42       ` Onur Özkan

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=AE29D511-8F4A-49A3-BE4E-31E6411816D7@collabora.com \
    --to=daniel.almeida@collabora.com \
    --cc=a.hindborg@kernel.org \
    --cc=airlied@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gary@garyguo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tmgross@umich.edu \
    --cc=work@onurozkan.dev \
    /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
all inboxes | Powered by JetHome®