From: <patrice.chotard-qxv4g6HH51o@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Maxime Coquelin
<mcoquelin.stm32-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Alexandre Torgue <alexandre.torgue-qxv4g6HH51o@public.gmane.org>,
<linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
<linux-stm32-XDFAJ8BFU24N7RejjzZ/Li2xQDfSxrLKVpNB7YpNyf8@public.gmane.org>,
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: <patrice.chotard-qxv4g6HH51o@public.gmane.org>,
<christophe.kerello-qxv4g6HH51o@public.gmane.org>
Subject: [PATCH 0/2] spi: stm32-qspi: rework probe error path
Date: Mon, 3 Feb 2020 14:50:46 +0100 [thread overview]
Message-ID: <20200203135048.1299-1-patrice.chotard@st.com> (raw)
From: Patrice Chotard <patrice.chotard-qxv4g6HH51o@public.gmane.org>
This series is fixing the probe error path of spi-stm32-qspi driver:
- it allows to defer probe if reset controller driver is not yet probed.
- if fixes the error path in releasing only allocated ressouces in case of error.
Etienne Carriere (1):
spi: stm32-qspi: defer probe for reset controller
Lionel Debieve (1):
spi: stm32-qspi: properly manage probe errors
drivers/spi/spi-stm32-qspi.c | 31 +++++++++++++++++++------------
1 file changed, 19 insertions(+), 12 deletions(-)
--
2.17.1
next reply other threads:[~2020-02-03 13:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 13:50 patrice.chotard-qxv4g6HH51o [this message]
[not found] ` <20200203135048.1299-1-patrice.chotard-qxv4g6HH51o@public.gmane.org>
2020-02-03 13:50 ` [PATCH 1/2] spi: stm32-qspi: defer probe for reset controller patrice.chotard-qxv4g6HH51o
2020-02-11 15:51 ` Applied "spi: stm32-qspi: defer probe for reset controller" to the spi tree Mark Brown
2020-02-03 13:50 ` [PATCH 2/2] spi: stm32-qspi: properly manage probe errors patrice.chotard
2020-02-11 15:51 ` Applied "spi: stm32-qspi: properly manage probe errors" to the spi tree Mark Brown
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=20200203135048.1299-1-patrice.chotard@st.com \
--to=patrice.chotard-qxv4g6hh51o@public.gmane.org \
--cc=alexandre.torgue-qxv4g6HH51o@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=christophe.kerello-qxv4g6HH51o@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-stm32-XDFAJ8BFU24N7RejjzZ/Li2xQDfSxrLKVpNB7YpNyf8@public.gmane.org \
--cc=mcoquelin.stm32-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 NNTP newsgroup(s).