From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Yangtao Li" <frank.li@vivo.com>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Daniel Lezcano" <daniel.lezcano@linaro.org>,
"Amit Kucheria" <amitk@kernel.org>,
"Zhang Rui" <rui.zhang@intel.com>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Jonathan Cameron" <Jonathan.Cameron@Huawei.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
linux-renesas-soc@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 14/22] drivers/thermal/rcar_gen3_thermal: convert to use devm_request*_irq_probe()
Date: Fri, 21 Jul 2023 11:56:08 +0200 [thread overview]
Message-ID: <fff3d307-485a-c271-1781-becbd18ec2c7@kernel.org> (raw)
In-Reply-To: <20230721094641.77189-14-frank.li@vivo.com>
On 21/07/2023 11:46, Yangtao Li wrote:
> There are more than 700 calls to devm_request_threaded_irq method and
> more than 1000 calls to devm_request_irq method. Most drivers only
> request one interrupt resource, and these error messages are basically
> the same. If error messages are printed everywhere, more than 2000 lines
> of code can be saved by removing the msg in the driver.
>
All your subject prefixes are totally mixed up.
Please use subject prefixes matching the subsystem. You can get them for
example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory
your patch is touching.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-07-21 9:56 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 9:46 [PATCH v5 01/22] genirq/devres: Add devm_request_threaded_irq_probe() and devm_request_irq_probe() Yangtao Li
2023-07-21 9:46 ` [PATCH v5 02/22] thermal/drivers/sun8i: convert to use devm_request*_irq_probe() Yangtao Li
2023-07-21 9:46 ` Yangtao Li
2023-07-21 10:45 ` Rafael J. Wysocki
2023-07-21 10:45 ` Rafael J. Wysocki
2024-08-29 3:02 ` 答复: " 李扬韬
2024-08-29 3:21 ` Yangtao Li
2024-08-29 13:17 ` Thomas Gleixner
2023-07-21 9:46 ` [PATCH v5 03/22] thermal/drivers/armada: " Yangtao Li
2023-07-21 9:46 ` [PATCH v5 04/22] thermal/drivers/broadcom: " Yangtao Li
2023-07-21 9:46 ` Yangtao Li
2023-07-21 9:46 ` [PATCH v5 05/22] thermal/drivers/tegra: " Yangtao Li
2023-07-21 9:55 ` Krzysztof Kozlowski
2023-07-21 9:46 ` [PATCH v5 06/22] thermal/drivers/qcom/lmh: " Yangtao Li
2023-07-21 9:46 ` [PATCH v5 07/22] thermal/drivers/db8500: " Yangtao Li
2023-07-21 9:46 ` [PATCH v5 08/22] thermal/drivers/rcar: " Yangtao Li
2023-07-21 9:46 ` [PATCH v5 09/22] thermal/drivers/qcom/temp-alarm: " Yangtao Li
2023-07-21 9:46 ` [PATCH v5 10/22] thermal: intel: int340x: processor_thermal: " Yangtao Li
2023-07-21 9:46 ` [PATCH v5 11/22] thermal/drivers/exynos: " Yangtao Li
2023-07-21 9:46 ` Yangtao Li
2023-07-21 9:46 ` [PATCH v5 12/22] thermal/drivers/hisi: " Yangtao Li
2023-07-21 9:46 ` [PATCH v5 13/22] thermal/drivers/rockchip: " Yangtao Li
2023-07-21 9:46 ` Yangtao Li
2023-07-21 9:46 ` Yangtao Li
2023-07-21 9:46 ` [PATCH v5 14/22] drivers/thermal/rcar_gen3_thermal: " Yangtao Li
2023-07-21 9:56 ` Krzysztof Kozlowski [this message]
2023-07-21 9:46 ` [PATCH v5 15/22] thermal/drivers/mediatek/lvts_thermal: " Yangtao Li
2023-07-21 9:46 ` Yangtao Li
2023-07-21 9:46 ` [PATCH v5 16/22] thermal: max77620: " Yangtao Li
2023-07-21 9:46 ` [PATCH v5 17/22] thermal/drivers/intel/bxt_pmic: " Yangtao Li
2023-07-21 9:46 ` [PATCH v5 18/22] thermal/drivers/stm: " Yangtao Li
2023-07-21 9:46 ` Yangtao Li
2023-07-21 9:46 ` [PATCH v5 19/22] thermal/drivers/qcom/tsens-v0_1: " Yangtao Li
2023-07-21 9:46 ` [PATCH v5 20/22] thermal: qcom-spmi-adc-tm5: " Yangtao Li
2023-07-21 9:46 ` [PATCH v5 21/22] thermal/drivers/uniphier: " Yangtao Li
2023-07-21 9:46 ` Yangtao Li
2023-07-21 9:46 ` [PATCH v5 22/22] thermal/drivers/imx: " Yangtao Li
2023-07-21 9:46 ` Yangtao Li
2024-08-29 3:41 ` [PATCH v5 01/22] genirq/devres: Add devm_request_threaded_irq_probe() and devm_request_irq_probe() Yangtao Li
2024-08-29 13:24 ` Thomas Gleixner
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=fff3d307-485a-c271-1781-becbd18ec2c7@kernel.org \
--to=krzk@kernel.org \
--cc=Jonathan.Cameron@Huawei.com \
--cc=amitk@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=daniel.lezcano@linaro.org \
--cc=frank.li@vivo.com \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=tglx@linutronix.de \
--cc=u.kleine-koenig@pengutronix.de \
/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.