From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Jan Kiszka <jan.kiszka@siemens.com>,
Kieran Bingham <kbingham@kernel.org>,
Tony Ambardar <tony.ambardar@gmail.com>,
Stephen Brennan <stephen.s.brennan@oracle.com>,
Shanker Donthineni <sdonthineni@nvidia.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v2] scripts/gdb: Fix interrupts.py after maple tree conversion
Date: Tue, 24 Jun 2025 19:01:42 -0700 [thread overview]
Message-ID: <b58954c7-cbc0-4971-81c8-8c40c1bb1f53@broadcom.com> (raw)
In-Reply-To: <20250624165000.ecf2a00a55fd267befa6fdb4@linux-foundation.org>
On 6/24/2025 4:50 PM, Andrew Morton wrote:
> On Mon, 23 Jun 2025 20:27:45 -0700 Florian Fainelli <florian.fainelli@broadcom.com> wrote:
>
>> In commit 721255b9826b ("genirq: Use a maple tree for interrupt
>> descriptor management"), the irq_desc_tree was replaced with a
>> sparse_irqs tree using a maple tree structure.
>>
>> A new module (mapletree.py) is added whose mtree_load() implementation
>> is largely copied after the C version and uses the same variable and
>> intermediate function names wherever possible to ensure that both the C
>> and Python version be updated in the future.
>
> butbutbut. What is actually being "fixed" here? The above contains no
> description of any problem.
OK, I also thought this was clear enough that the script stopped working
and printed nothing, but does not hurt to state that clearly. v3 coming
up shortly, thanks!
--
Florian
prev parent reply other threads:[~2025-06-25 2:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 3:27 Florian Fainelli
2025-06-24 23:50 ` Andrew Morton
2025-06-25 2:01 ` Florian Fainelli [this message]
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=b58954c7-cbc0-4971-81c8-8c40c1bb1f53@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=akpm@linux-foundation.org \
--cc=jan.kiszka@siemens.com \
--cc=kbingham@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sdonthineni@nvidia.com \
--cc=stephen.s.brennan@oracle.com \
--cc=tglx@linutronix.de \
--cc=tony.ambardar@gmail.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 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®