From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Marco Crivellari <marco.crivellari@suse.com>
Cc: <linux-kernel@vger.kernel.org>, <intel-gfx@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>, Tejun Heo <tj@kernel.org>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Frederic Weisbecker <frederic@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Michal Hocko <mhocko@suse.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Tvrtko Ursulin <tursulin@ursulin.net>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
"Krzysztof Karas" <krzysztof.karas@intel.com>
Subject: Re: [PATCH v3 0/3] replace old wq(s), add WQ_PERCPU to alloc_workqueue
Date: Thu, 5 Mar 2026 14:00:26 -0500 [thread overview]
Message-ID: <aanSyqBzTygkzg80@intel.com> (raw)
In-Reply-To: <aanRQseClNRRDZxq@intel.com>
On Thu, Mar 05, 2026 at 01:53:58PM -0500, Rodrigo Vivi wrote:
> On Thu, Mar 05, 2026 at 04:04:32PM +0100, Marco Crivellari wrote:
> > Hi,
> >
> > On Tue, Nov 4, 2025 at 11:00 AM Marco Crivellari
> > <marco.crivellari@suse.com> wrote:
> > > Marco Crivellari (3):
> > > drm/i915: replace use of system_unbound_wq with system_dfl_wq
> > > drm/i915: replace use of system_wq with system_percpu_wq in the
> > > documentation
> > > drm/i915: add WQ_PERCPU to alloc_workqueue users
> >
> > Gentle ping.
> > I checked patchwork and seems still in the "New" state.
>
> Please ignore patchwork status.
>
> Both patches queued towards the next merge window targeting 7.1
>
> fa171b805f25 ("drm/xe: replace use of system_unbound_wq with system_dfl_wq")
> 0bc2c2e1a388 ("drm/xe: add WQ_PERCPU to alloc_workqueue users")
doh! please ignore me.
The similar subject titles confused me.
I just pushed this i915 series to drm-intel-next.
Now, also queued for 7.1 along with the xe above.
c15d0056fb74 drm/i915: add WQ_PERCPU to alloc_workqueue users
4fb289d352e3 drm/i915: replace use of system_wq with system_percpu_wq in the documentation
36ed3648a2f3 drm/i915: replace use of system_unbound_wq with system_dfl_wq
>
> Thanks,
> Rodrigo.
>
> >
> > Thanks!
> >
> > --
> >
> > Marco Crivellari
> >
> > L3 Support Engineer
next prev parent reply other threads:[~2026-03-05 19:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 10:00 [PATCH v3 0/3] replace old wq(s), add WQ_PERCPU to alloc_workqueue Marco Crivellari
2025-11-04 10:00 ` [PATCH v3 1/3] drm/i915: replace use of system_unbound_wq with system_dfl_wq Marco Crivellari
2025-11-04 10:00 ` [PATCH v3 2/3] drm/i915: replace use of system_wq with system_percpu_wq in the documentation Marco Crivellari
2025-11-04 10:00 ` [PATCH v3 3/3] drm/i915: add WQ_PERCPU to alloc_workqueue users Marco Crivellari
2025-11-05 8:41 ` [PATCH v3 0/3] replace old wq(s), add WQ_PERCPU to alloc_workqueue Krzysztof Karas
2025-11-05 8:56 ` Marco Crivellari
2025-11-10 12:11 ` Jani Nikula
2026-01-13 9:12 ` Marco Crivellari
2026-03-05 15:04 ` Marco Crivellari
2026-03-05 18:53 ` Rodrigo Vivi
2026-03-05 19:00 ` Rodrigo Vivi [this message]
2026-03-06 8:16 ` Marco Crivellari
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=aanSyqBzTygkzg80@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=airlied@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=frederic@kernel.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jiangshanlai@gmail.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=krzysztof.karas@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.crivellari@suse.com \
--cc=mhocko@suse.com \
--cc=simona@ffwll.ch \
--cc=tj@kernel.org \
--cc=tursulin@ursulin.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