From: "Danilo Krummrich" <dakr@kernel.org>
To: "Koen Koning" <koen.koning@linux.intel.com>
Cc: "Joel Fernandes" <joelagnelf@nvidia.com>,
"Greg KH" <gregkh@linuxfoundation.org>,
<dri-devel@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>,
"Matthew Auld" <matthew.auld@intel.com>,
"Dave Airlie" <airlied@redhat.com>,
"Peter Senna Tschudin" <peter.senna@linux.intel.com>,
<stable@vger.kernel.org>
Subject: Re: [PATCH v3 1/3] gpu/buddy: fix module_init() usage
Date: Mon, 23 Feb 2026 12:20:23 +0100 [thread overview]
Message-ID: <DGMAUQLZGPZB.FWELZM9GYP0Z@kernel.org> (raw)
In-Reply-To: <b45a50ce-de96-42ee-90c1-0a6cd7a78cc0@linux.intel.com>
On Mon Feb 23, 2026 at 12:17 PM CET, Koen Koning wrote:
> Thanks that makes sense, then let's just stick to addressing the current
> regression with gpu/buddy in the drm-tip tree.
The patch should go into drm-misc-next.
> Joel, could you grab the v1 of this patchset (or the v2 with with
> subsys_initcall, either works) and try to get it applied to drm-tip?
> Since this is my first time submitting patches, I'm not really sure how
> to proceed from here, and it will probably be faster if you have a look.
I think we should land your original v1; I don't know if Joel can push to
drm-misc-next, if not please let me know, I can pick it up then.
next prev parent reply other threads:[~2026-02-23 11:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260216111902.110286-1-koen.koning@linux.intel.com>
[not found] ` <20260219213858.370675-1-koen.koning@linux.intel.com>
2026-02-19 21:38 ` [PATCH v3 1/3] gpu/buddy: fix module_init() usage Koen Koning
2026-02-20 6:06 ` Greg KH
2026-02-20 10:17 ` Danilo Krummrich
2026-02-20 13:55 ` Joel Fernandes
2026-02-21 5:44 ` Greg KH
2026-02-23 0:49 ` Joel Fernandes
2026-02-23 11:17 ` Koen Koning
2026-02-23 11:20 ` Danilo Krummrich [this message]
2026-02-23 13:42 ` Joel Fernandes
2026-02-23 22:31 ` Danilo Krummrich
2026-02-24 3:41 ` David Airlie
2026-02-19 21:38 ` [PATCH v3 2/3] drm/sched: " Koen Koning
2026-02-20 6:06 ` Greg KH
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=DGMAUQLZGPZB.FWELZM9GYP0Z@kernel.org \
--to=dakr@kernel.org \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=joelagnelf@nvidia.com \
--cc=koen.koning@linux.intel.com \
--cc=matthew.auld@intel.com \
--cc=peter.senna@linux.intel.com \
--cc=stable@vger.kernel.org \
/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