From: Thomas Gleixner <tglx@linutronix.de>
To: Charles Mirabile <cmirabil@redhat.com>
Cc: alex@ghiti.fr, aou@eecs.berkeley.edu, cmirabil@redhat.com,
conor+dt@kernel.org, devicetree@vger.kernel.org,
dramforever@live.com, krzk+dt@kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
lzampier@redhat.com, palmer@dabbelt.com,
paul.walmsley@sifive.com, robh@kernel.org,
samuel.holland@sifive.com, zhangxincheng@ultrarisc.com
Subject: Re: [PATCH v5 3/3] irqchip/plic: add support for UltraRISC DP1000 PLIC
Date: Fri, 17 Oct 2025 15:28:59 +0200 [thread overview]
Message-ID: <87plalzmg4.ffs@tglx> (raw)
In-Reply-To: <20251016195902.338629-1-cmirabil@redhat.com>
On Thu, Oct 16 2025 at 15:58, Charles Mirabile wrote:
> On Thu, Oct 16, 2025 at 07:53:26PM +0200, Thomas Gleixner wrote:
> What do you think about the attached patch (it should be not corrupt :^)
> I think I adressed your concerns, and I ran it through clang-format too.
>
> I folded everything into one diff for ease of review, but when we send it
> officially there will be a separate patch for the caching refactor.
Looks about right and it's a net win for everyone due to the suspend
path cleanup.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Gleixner <tglx@linutronix.de>
To: Charles Mirabile <cmirabil@redhat.com>
Cc: alex@ghiti.fr, aou@eecs.berkeley.edu, cmirabil@redhat.com,
conor+dt@kernel.org, devicetree@vger.kernel.org,
dramforever@live.com, krzk+dt@kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
lzampier@redhat.com, palmer@dabbelt.com,
paul.walmsley@sifive.com, robh@kernel.org,
samuel.holland@sifive.com, zhangxincheng@ultrarisc.com
Subject: Re: [PATCH v5 3/3] irqchip/plic: add support for UltraRISC DP1000 PLIC
Date: Fri, 17 Oct 2025 15:28:59 +0200 [thread overview]
Message-ID: <87plalzmg4.ffs@tglx> (raw)
In-Reply-To: <20251016195902.338629-1-cmirabil@redhat.com>
On Thu, Oct 16 2025 at 15:58, Charles Mirabile wrote:
> On Thu, Oct 16, 2025 at 07:53:26PM +0200, Thomas Gleixner wrote:
> What do you think about the attached patch (it should be not corrupt :^)
> I think I adressed your concerns, and I ran it through clang-format too.
>
> I folded everything into one diff for ease of review, but when we send it
> officially there will be a separate patch for the caching refactor.
Looks about right and it's a net win for everyone due to the suspend
path cleanup.
next prev parent reply other threads:[~2025-10-17 13:29 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 8:42 [PATCH v5 0/3] Add UltraRISC DP1000 PLIC support Lucas Zampieri
2025-10-16 8:42 ` Lucas Zampieri
2025-10-16 8:42 ` [PATCH v5 1/3] dt-bindings: vendor-prefixes: add UltraRISC Lucas Zampieri
2025-10-16 8:42 ` [PATCH v5 2/3] dt-bindings: interrupt-controller: add UltraRISC DP1000 PLIC Lucas Zampieri
2025-10-16 8:42 ` Lucas Zampieri
2025-10-16 8:42 ` [PATCH v5 3/3] irqchip/plic: add support for " Lucas Zampieri
2025-10-16 8:42 ` Lucas Zampieri
2025-10-16 10:16 ` Thomas Gleixner
2025-10-16 10:16 ` Thomas Gleixner
2025-10-17 11:52 ` Lucas Zampieri
2025-10-17 11:52 ` Lucas Zampieri
2025-10-16 13:17 ` Thomas Gleixner
2025-10-16 13:17 ` Thomas Gleixner
2025-10-16 15:54 ` Charles Mirabile
2025-10-16 15:54 ` Charles Mirabile
2025-10-16 16:12 ` Thomas Gleixner
2025-10-16 16:12 ` Thomas Gleixner
2025-10-16 16:52 ` Charles Mirabile
2025-10-16 16:52 ` Charles Mirabile
2025-10-16 17:53 ` Thomas Gleixner
2025-10-16 17:53 ` Thomas Gleixner
2025-10-16 19:58 ` Charles Mirabile
2025-10-16 19:58 ` Charles Mirabile
2025-10-17 13:28 ` Thomas Gleixner [this message]
2025-10-17 13:28 ` Thomas Gleixner
2025-10-16 21:09 ` Bo Gan
2025-10-16 21:09 ` Bo Gan
2025-10-16 21:28 ` Bo Gan
2025-10-16 21:28 ` Bo Gan
2025-10-16 22:01 ` Samuel Holland
2025-10-16 22:01 ` Samuel Holland
2025-10-16 23:19 ` Bo Gan
2025-10-16 23:19 ` Bo Gan
2025-10-16 23:25 ` Charles Mirabile
2025-10-16 23:25 ` Charles Mirabile
2025-10-17 21:25 ` Bo Gan
2025-10-17 21:25 ` Bo Gan
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=87plalzmg4.ffs@tglx \
--to=tglx@linutronix.de \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=cmirabil@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dramforever@live.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lzampier@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=zhangxincheng@ultrarisc.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.