linux-kernel - Re: [PATCH v8 0/1] genirq/devres: Add dev_err_probe() in devm_request_threaded_irq() and devm_request_any_context

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20250730061128.259744-1-panchuang@vivo.com>
Date: Wed, 30 Jul 2025 14:11:28 +0800
From: Pan Chuang <panchuang@...o.com>
To: Markus.Elfring@....de
Cc: kernel-janitors@...r.kernel.org,
	tglx@...utronix.de,
	linux-kernel@...r.kernel.org,
	miquel.raynal@...tlin.com,
	Jonathan.Cameron@...wei.com,
	u.kleine-koenig@...gutronix.de,
	angeg.delregno@...labora.com,
	krzk@...nel.org,
	a.fatoum@...gutronix.de,
	frank.li@...o.com
Subject: Re: [PATCH v8 0/1] genirq/devres: Add dev_err_probe() in devm_request_threaded_irq() and devm_request_any_context_irq()

Hi, Markus
On Wed, Jul 30, 2025 at 2:35 AM, Markus Elfring wrote:
> …
>> This patch implements a standardized error reporting approach[1]:
> …
>
> Would it become helpful to move any information from the cover letter
> to the (single) patch?
> How do you think about to avoid the presentation of duplicate data?
Thank you for your suggestion.

To ensure commit message conciseness, we only describe:

    The context and problem being addressed.

    A brief summary of the solution.

Regarding duplicate error messages:

    The failure probability is low, so temporary duplication is acceptable for now.

    We will remove the random printks from the drivers, once the core change 
    has hit upstream.

Thanks,

	PanChuang