Linux-i2c Archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: Alain Volmat <alain.volmat@foss.st.com>
Cc: Andi Shyti <andi.shyti@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Alexandre Torgue <alexandre.torgue@foss.st.com>,
	Pierre-Yves MORDRET <pierre-yves.mordret@foss.st.com>,
	Conor Dooley <conor@kernel.org>,
	linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/9] i2c: stm32f7: simplify status messages in case of errors
Date: Fri, 22 Dec 2023 11:45:06 +0100	[thread overview]
Message-ID: <ZYVosiRTD2w9sVV+@shikoro> (raw)
In-Reply-To: <20231215170617.95868-4-alain.volmat@foss.st.com>

[-- Attachment #1: Type: text/plain, Size: 373 bytes --]

On Fri, Dec 15, 2023 at 06:06:07PM +0100, Alain Volmat wrote:
> Avoid usage of __func__ when reporting an error message
> since dev_err/dev_dbg are already providing enough details
> to identify the source of the message.
> 
> Signed-off-by: Alain Volmat <alain.volmat@foss.st.com>
> Reviewed-by: Andi Shyti <andi.shyti@kernel.org>

Applied to for-next, thanks!


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-12-22 10:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-15 17:06 [PATCH v3 0/9] i2c: stm32f7: enhancements and support for stm32mp25 Alain Volmat
2023-12-15 17:06 ` [PATCH v3 1/9] i2c: stm32f7: use dev_err_probe upon calls of devm_request_irq Alain Volmat
2023-12-22 10:44   ` Wolfram Sang
2023-12-15 17:06 ` [PATCH v3 2/9] i2c: stm32f7: perform most of irq job in threaded handler Alain Volmat
2023-12-22 10:44   ` Wolfram Sang
2023-12-15 17:06 ` [PATCH v3 3/9] i2c: stm32f7: simplify status messages in case of errors Alain Volmat
2023-12-22 10:45   ` Wolfram Sang [this message]
2023-12-15 17:06 ` [PATCH v3 4/9] dt-bindings: i2c: document st,stm32mp25-i2c compatible Alain Volmat
2023-12-22 10:45   ` Wolfram Sang
2023-12-15 17:06 ` [PATCH v3 5/9] i2c: stm32f7: perform I2C_ISR read once at beginning of event isr Alain Volmat
2023-12-22 10:45   ` Wolfram Sang
2023-12-15 17:06 ` [PATCH v3 6/9] i2c: stm32f7: add support for stm32mp25 soc Alain Volmat
2023-12-22 10:45   ` Wolfram Sang
2023-12-15 17:06 ` [PATCH v3 7/9] arm64: dts: st: add all 8 i2c nodes on stm32mp251 Alain Volmat
2023-12-15 17:06 ` [PATCH v3 8/9] arm64: dts: st: add i2c2/i2c8 pins for stm32mp25 Alain Volmat
2023-12-15 17:06 ` [PATCH v3 9/9] arm64: dts: st: add i2c2 / i2c8 properties on stm32mp257f-ev1 Alain Volmat
2024-04-25  8:00 ` [PATCH v3 0/9] i2c: stm32f7: enhancements and support for stm32mp25 Alexandre TORGUE

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=ZYVosiRTD2w9sVV+@shikoro \
    --to=wsa@kernel.org \
    --cc=alain.volmat@foss.st.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=andi.shyti@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=pierre-yves.mordret@foss.st.com \
    --cc=robh+dt@kernel.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).