From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: jic23@kernel.org, knaack.h@gmx.de, lars@metafoo.de,
pmeerw@pmeerw.net, sre@kernel.org, wsa@the-dreams.de,
kishon@ti.com
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Subject: [PATCH 0/3] iio: adc: twl4030: Fix some error handling issues in 'twl4030_madc_probe()'
Date: Sat, 23 Sep 2017 08:03:34 +0200 [thread overview]
Message-ID: <cover.1506146101.git.christophe.jaillet@wanadoo.fr> (raw)
These 3 patches are all related to error hangling in 'twl4030_madc_probe()'.
They are also all related to commit 7cc97d77ee8a
("iio: adc: twl4030: Fix ADC[3:6] readings")
The semantic of the patches behing slighly different:
- direct return instead of going through the error handling path
- missing function in the error handling path
- spurious pattern (IMO) if unable to enable a regulator
I have splitted them in 3 parts.
Christophe JAILLET (3):
iio: adc: twl4030: Fix an error handling path in
'twl4030_madc_probe()'
iio: adc: twl4030: Disable the vusb3v1 rugulator in the error handling
path of 'twl4030_madc_probe()'
iio: adc: twl4030: Return an error if we can not enable the vusb3v1
regulator in 'twl4030_madc_probe()'
drivers/iio/adc/twl4030-madc.c | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)
--
2.11.0
next reply other threads:[~2017-09-23 6:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-23 6:03 Christophe JAILLET [this message]
2017-09-23 6:06 ` [PATCH 1/3] iio: adc: twl4030: Fix an error handling path " Christophe JAILLET
2017-09-24 11:58 ` Jonathan Cameron
2017-09-23 6:06 ` [PATCH 2/3] iio: adc: twl4030: Disable the vusb3v1 rugulator in the error handling path of 'twl4030_madc_probe()' Christophe JAILLET
2017-09-24 12:00 ` Jonathan Cameron
2017-09-23 6:06 ` [PATCH 3/3] iio: adc: twl4030: Return an error if we can not enable the vusb3v1 regulator in 'twl4030_madc_probe()' Christophe JAILLET
2017-09-24 12:05 ` Jonathan Cameron
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=cover.1506146101.git.christophe.jaillet@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=jic23@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kishon@ti.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=sre@kernel.org \
--cc=wsa@the-dreams.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome