public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-rt-devel@lists.linux.dev,
	"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
	John Ogness <john.ogness@linutronix.de>,
	Lai Jiangshan <jiangshanlai@gmail.com>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>
Subject: Re: [PATCH v2 1/2] workqueue: Allow to expose ordered workqueues via sysfs
Date: Fri, 27 Feb 2026 07:27:15 -1000	[thread overview]
Message-ID: <aaHT862yav5XxHMY@slm.duckdns.org> (raw)
In-Reply-To: <98bc8bdf-e658-4018-a816-6cd75baaff9c@app.fastmail.com>

On Fri, Feb 27, 2026 at 06:20:47PM +0100, Ard Biesheuvel wrote:
> 
> 
> On Fri, 27 Feb 2026, at 18:14, Sebastian Andrzej Siewior wrote:
> > On 2026-02-27 07:12:46 [-1000], Tejun Heo wrote:
> >> Acked-by: Tejun Heo <tj@kernel.org>
> > Thank.
> >
> >> I can apply this to wq/for-7.1. Would that work?
> >
> > I think you need to take both since 2/2 can't be applied independently.
> > Maybe Ard is going to give his blessing ;)
> >
> 
> iIRC I already acked v1.

Ard, do you want me to take both patches or wann pull from wq/for-7.1?

Thanks.

-- 
tejun

  reply	other threads:[~2026-02-27 17:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27 17:01 [PATCH v2 0/2] efi: Expose the runtime-services workqueue via sysfs Sebastian Andrzej Siewior
2026-02-27 17:01 ` [PATCH v2 1/2] workqueue: Allow to expose ordered workqueues " Sebastian Andrzej Siewior
2026-02-27 17:12   ` Tejun Heo
2026-02-27 17:14     ` Sebastian Andrzej Siewior
2026-02-27 17:20       ` Ard Biesheuvel
2026-02-27 17:27         ` Tejun Heo [this message]
2026-02-27 17:36           ` Ard Biesheuvel
2026-02-27 17:01 ` [PATCH v2 2/2] efi: Allow to expose the workqueue " Sebastian Andrzej Siewior
2026-02-27 19:10 ` [PATCH v2 0/2] efi: Expose the runtime-services " Tejun Heo

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=aaHT862yav5XxHMY@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=ardb@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=ilias.apalodimas@linaro.org \
    --cc=jiangshanlai@gmail.com \
    --cc=john.ogness@linutronix.de \
    --cc=lgoncalv@redhat.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-devel@lists.linux.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