From: Alain Volmat <alain.volmat@st.com>
To: <wsa@kernel.org>, <pierre-yves.mordret@st.com>
Cc: <alexandre.torgue@st.com>, <linux-i2c@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <fabrice.gasnier@st.com>,
<krzk@kernel.org>, <h.assmann@pengutronix.de>,
<alain.volmat@st.com>
Subject: [PATCH 0/2] Avoid meaningless DMA error print & use dev_err_probe
Date: Mon, 14 Sep 2020 12:40:32 +0200 [thread overview]
Message-ID: <1600080034-2050-1-git-send-email-alain.volmat@st.com> (raw)
This serie replaces the patch from Holger Assmann [i2c: stm32: remove
unnecessary DMA kernel error log] (1) and the first version of [i2c: stm32:
do not display error when DMA is not requested] from myself (2).
A first patch is fixing useless error print when not being able to get
DMA channel (DMA is only optional) and also avoid printing twice an error
when a real DMA error is happening.
On top of that, dev_err_probe from Krzysztof has been rebased.
[1] https://marc.info/?l=linux-i2c&m=159741480608578&w=2
[2] https://marc.info/?l=linux-i2c&m=159973040314193&w=2
Alain Volmat (1):
i2c: stm32: fix error message on upon dma_request_chan & defer
handling
Krzysztof Kozlowski (1):
i2c: stm32: Simplify with dev_err_probe()
drivers/i2c/busses/i2c-stm32.c | 12 ++++++------
drivers/i2c/busses/i2c-stm32f4.c | 6 ++----
drivers/i2c/busses/i2c-stm32f7.c | 27 +++++++++++----------------
3 files changed, 19 insertions(+), 26 deletions(-)
--
2.7.4
next reply other threads:[~2020-09-14 10:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 10:40 Alain Volmat [this message]
2020-09-14 10:40 ` [PATCH 1/2] i2c: stm32: fix error message on upon dma_request_chan & defer handling Alain Volmat
2020-09-14 10:40 ` [PATCH v2 2/2] i2c: stm32: Simplify with dev_err_probe() Alain Volmat
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=1600080034-2050-1-git-send-email-alain.volmat@st.com \
--to=alain.volmat@st.com \
--cc=alexandre.torgue@st.com \
--cc=fabrice.gasnier@st.com \
--cc=h.assmann@pengutronix.de \
--cc=krzk@kernel.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=pierre-yves.mordret@st.com \
--cc=wsa@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
all inboxes | Powered by JetHome®