From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Marco Crivellari <marco.crivellari@suse.com>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
kernel@collabora.com
Cc: 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>,
Shreeya Patel <shreeya.patel@collabora.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [PATCH] media: synopsys: hdmirx: replace use of system_unbound_wq with system_dfl_wq
Date: Tue, 10 Feb 2026 00:18:34 +0300 [thread overview]
Message-ID: <2b5e55c8-6790-4de5-912b-9ca23f6bd7a5@collabora.com> (raw)
In-Reply-To: <f8522806-fc3a-403c-93ad-f37638870643@collabora.com>
On 2/9/26 23:46, Dmitry Osipenko wrote:
> On 2/4/26 14:49, Marco Crivellari wrote:
>> On Tue, Nov 4, 2025 at 11:23 AM Marco Crivellari
>> <marco.crivellari@suse.com> wrote:
>>> [...]
>>> drivers/media/platform/synopsys/hdmirx/snps_hdmirx.c | 8 ++++----
>>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> Gentle ping.
>>
>> Thanks!
>>
>
> Would be good to have a reply from Tejun as I feel confused by the two
> "identical" unbound workqueues. What happens if one part of kernel
> queues work items to old unbound wq and other queues to new system_dfl
> at the same time such that all workers are busy?
Alright, looking further at the code, apparently there is nothing
special RE the two unbound work queues. See some parts of kernel already
moved to system_dfl. Would be great is this all was clarified in the
commit message.
Acked-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
--
Best regards,
Dmitry
next prev parent reply other threads:[~2026-02-09 21:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 10:20 Marco Crivellari
2025-11-04 12:45 ` Dmitry Osipenko
2025-11-04 16:44 ` Marco Crivellari
2026-02-04 11:49 ` Marco Crivellari
2026-02-09 20:46 ` Dmitry Osipenko
2026-02-09 21:18 ` Dmitry Osipenko [this message]
2026-02-10 14:36 ` Marco Crivellari
2026-02-11 16:45 ` Dmitry Osipenko
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=2b5e55c8-6790-4de5-912b-9ca23f6bd7a5@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=marco.crivellari@suse.com \
--cc=mchehab@kernel.org \
--cc=mhocko@suse.com \
--cc=shreeya.patel@collabora.com \
--cc=tj@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
all inboxes | Powered by JetHome®