From: Thomas Gleixner <tglx@linutronix.de>
To: "Björn Töpel" <bjorn@kernel.org>, "Anup Patel" <apatel@ventanamicro.com>
Cc: "Anup Patel" <anup@brainfault.org>,
"Björn Töpel" <bjorn@rivosinc.com>,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
x86@kernel.org, "Marc Zyngier" <maz@kernel.org>
Subject: Re: [RFC PATCH] genirq/matrix: Dynamic bitmap allocation
Date: Fri, 27 Oct 2023 01:17:34 +0200 [thread overview]
Message-ID: <87fs1x3re9.ffs@tglx> (raw)
In-Reply-To: <87a5s5z44x.fsf@all.your.base.are.belong.to.us>
On Thu, Oct 26 2023 at 19:26, Björn Töpel wrote:
> Note that the per-device domain support is already upstream, it's only
> the ARM cleanups that are not.
>
> IOW, there's no need to wait for the ARM cleanups. :-)
Correct. The &*@^@#%$ delayed ARM link was only meant as a reference on
how this is implemented and obviously as a reminder to the ARM folks to
get this finally done...
The main point is not to introduce new users of this failed programming
model and instead make them use the more future proof implementation
right away - which of course might to turn out to be completely wrong
5-10 years from now :)
Thanks,
tglx
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-10-26 23:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 10:19 [RFC PATCH] genirq/matrix: Dynamic bitmap allocation Björn Töpel
2023-10-26 10:41 ` Thomas Gleixner
2023-10-26 12:26 ` Anup Patel
2023-10-26 17:26 ` Björn Töpel
2023-10-26 23:17 ` Thomas Gleixner [this message]
2023-10-27 4:31 ` Anup Patel
2023-10-27 9:08 ` Thomas Gleixner
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=87fs1x3re9.ffs@tglx \
--to=tglx@linutronix.de \
--cc=anup@brainfault.org \
--cc=apatel@ventanamicro.com \
--cc=bjorn@kernel.org \
--cc=bjorn@rivosinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maz@kernel.org \
--cc=x86@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