From: Thomas Gleixner <tglx@kernel.org>
To: Kemeng Shi <shikemeng@huaweicloud.com>, maz@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, shikemeng@huaweicloud.com
Subject: Re: [PATCH v3 4/6] irqchip/gic-v3-its: Add ITS address info in more error logs
Date: Tue, 30 Jun 2026 18:43:51 +0200 [thread overview]
Message-ID: <87zf0cou60.ffs@fw13> (raw)
In-Reply-To: <20260623020135.3584-5-shikemeng@huaweicloud.com>
On Tue, Jun 23 2026 at 10:01, Kemeng Shi wrote:
> We have a lot of logs containing ITS address info which is helpful to
We have nothing ...
> distiguish which ITS occurs error. Just add ITS address info into more
> exsiting error logs.
existing
'Just add ITS ...' does tell WHAT the patch does but does not explian
WHY this is required, useful or whatever reason you have.
next prev parent reply other threads:[~2026-06-30 16:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 2:01 [PATCH v3 0/6] Some Minor fixes and cleanups to Kemeng Shi
2026-06-23 2:01 ` [PATCH v3 1/6] irqchip/gic-v3-its: Fix memleak in its_probe_one() Kemeng Shi
2026-06-30 16:40 ` Thomas Gleixner
2026-06-23 2:01 ` [PATCH v3 2/6] irqchip/gic-v3-its: Fix its node leak in gic_acpi_parse_madt_its() Kemeng Shi
2026-06-30 16:40 ` Thomas Gleixner
2026-06-23 2:01 ` [PATCH v3 3/6] irqchip/gic-v3-its: Fix leak in its_vpe_irq_domain_alloc() Kemeng Shi
2026-06-30 16:42 ` Thomas Gleixner
2026-06-23 2:01 ` [PATCH v3 4/6] irqchip/gic-v3-its: Add ITS address info in more error logs Kemeng Shi
2026-06-30 16:43 ` Thomas Gleixner [this message]
2026-06-23 2:01 ` [PATCH v3 5/6] irqchip/gic-v3-its: some minor improvement in comments Kemeng Shi
2026-06-30 16:46 ` Thomas Gleixner
2026-07-02 2:46 ` Kemeng Shi
2026-06-23 2:01 ` [PATCH v3 6/6] irqchip/gic-v3-its: Remove redundant check in its_vpe_db_proxy_unmap_locked() Kemeng Shi
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=87zf0cou60.ffs@fw13 \
--to=tglx@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=shikemeng@huaweicloud.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