From: Jonathan Corbet <corbet@lwn.net>
To: Thomas Gleixner <tglx@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Aaron Tomlin <atomlin@atomlin.com>,
Christoph Hellwig <hch@lst.de>,
Frederic Weisbecker <frederic@kernel.org>,
Jens Axboe <axboe@fb.com>, Ming Lei <ming.lei@redhat.com>,
Valentin Schneider <vschneid@redhat.com>,
Waiman Long <longman@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
John Ogness <john.ogness@linutronix.de>
Subject: Re: [RFC PATCH] Documentation: Add managed interrupts
Date: Sat, 11 Apr 2026 07:08:48 -0600 [thread overview]
Message-ID: <871pgl1w67.fsf@trenco.lwn.net> (raw)
In-Reply-To: <87qzomzv8q.ffs@tglx>
Thomas Gleixner <tglx@kernel.org> writes:
> On Thu, Apr 09 2026 at 08:32, Jonathan Corbet wrote:
>>> This documents what we have as of today and how it works. I added some
>>> examples how the parameter affects the configuration. Did I miss
>>> something?
>>
>> There's been a lot of silence on this one... should I pick this one up,
>> or are there other plans for it...?
>
> Looks good to me.
>
> Acked-by: Thomas Gleixner <tglx@kernel.org>
OK, I've applied it, thanks.
jon
next prev parent reply other threads:[~2026-04-11 13:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 11:02 [RFC PATCH] Documentation: Add managed interrupts Sebastian Andrzej Siewior
2026-04-09 14:32 ` Jonathan Corbet
2026-04-10 15:32 ` Thomas Gleixner
2026-04-11 13:08 ` Jonathan Corbet [this message]
2026-04-10 16:59 ` Aaron Tomlin
2026-04-11 12:18 ` Ming Lei
2026-04-13 15:53 ` Sebastian Andrzej Siewior
2026-04-15 9:05 ` Ming Lei
2026-04-13 10:45 ` Valentin Schneider
2026-04-13 12:19 ` John Ogness
2026-04-13 15:59 ` Sebastian Andrzej Siewior
2026-04-13 15:57 ` Sebastian Andrzej Siewior
2026-04-14 20:10 ` Aaron Tomlin
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=871pgl1w67.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=atomlin@atomlin.com \
--cc=axboe@fb.com \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=hch@lst.de \
--cc=john.ogness@linutronix.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=ming.lei@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@kernel.org \
--cc=vschneid@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.