[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <D4KCJ2SLGMWG.1ZGZRDMNDKAVD@helene.moe>
Date: Tue, 01 Oct 2024 11:02:11 +0200
From: Hélène Vulquin <oss@...ene.moe>
To: "Dragan Simic" <dsimic@...jaro.org>, <linux-spi@...r.kernel.org>,
<linux-rockchip@...ts.infradead.org>
Cc: <broonie@...nel.org>, <heiko@...ech.de>, <gregkh@...uxfoundation.org>,
<rafael@...nel.org>, <linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 4/5] driver core: Add device probe log helper
dev_warn_probe()
On Sun Sep 29, 2024 at 11:21 AM CEST, Dragan Simic wrote:
> Some drivers can still provide their functionality to a certain extent even
> some of their resource acquisitions eventually fail. In such cases, emitting
> errors isn't the desired action, but warnings should be emitted instead.
>
> To solve this, introduce dev_warn_probe() as a new device probe log helper,
> which behaves identically as the already existing dev_err_probe(), while it
> produces warnings instead of errors. The intended use is with the resources
> that are actually optional for a particular driver.
>
> While there, copyedit the kerneldoc for dev_err_probe() a bit, to simplify
> its wording a bit, and reuse it as the kerneldoc for dev_warn_probe(), with
> the necessary wording adjustments, of course.
>
> Signed-off-by: Dragan Simic <dsimic@...jaro.org>
Applied and tested on 6.11 for arm64 without noticing any issues.
Tested-by: Hélène Vulquin <oss@...ene.moe>
Powered by blists - more mailing lists