The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Pan Chuang <panchuang@vivo.com>, Yangtao Li <frank.li@vivo.com>,
	kernel-janitors@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
	"Ahmad Fatoum" <a.fatoum@pengutronix.de>,
	"Angelo Gioacchino Del Regno"
	<angelogioacchino.delregno@collabora.com>,
	"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
	"Krzysztof Kozlowski" <krzk@kernel.org>,
	"Miquel Raynal" <miquel.raynal@bootlin.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Subject: Re: [PATCH v8 0/1] genirq/devres: Add dev_err_probe() in devm_request_threaded_irq() and devm_request_any_context_irq()
Date: Tue, 29 Jul 2025 20:35:53 +0200	[thread overview]
Message-ID: <5c0837b5-b3d3-48c2-a028-97cfcd1ec4fe@web.de> (raw)
In-Reply-To: <20250729081434.497716-1-panchuang@vivo.com>

…
> 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?

Regards,
Markus

  parent reply	other threads:[~2025-07-29 18:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-29  8:14 [PATCH v8 0/1] genirq/devres: Add dev_err_probe() in devm_request_threaded_irq() and devm_request_any_context_irq() Pan Chuang
2025-07-29  8:14 ` [PATCH v8 1/1] " Pan Chuang
2025-07-29  8:20   ` Ahmad Fatoum
2025-07-29  9:15     ` Thomas Gleixner
2025-07-29  9:14   ` Thomas Gleixner
2025-07-29 11:48     ` Pan Chuang
2025-07-29 12:12       ` Thomas Gleixner
2025-07-29 18:35 ` Markus Elfring [this message]
2025-07-30  6:11   ` [PATCH v8 0/1] " Pan Chuang

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=5c0837b5-b3d3-48c2-a028-97cfcd1ec4fe@web.de \
    --to=markus.elfring@web.de \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=a.fatoum@pengutronix.de \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=frank.li@vivo.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=panchuang@vivo.com \
    --cc=tglx@linutronix.de \
    --cc=u.kleine-koenig@baylibre.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