linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Kepplinger <martink@posteo.de>
To: Gregor Boirie <gregor.boirie@parrot.com>,
	linux-iio@vger.kernel.org,
	Daniel Baluta <daniel.baluta@intel.com>
Subject: Re: [PATCH v5 1/1] Fixes: 3145229f9191 ("iio:pressure:ms5611: power regulator support")
Date: Wed, 9 Mar 2016 11:06:12 +0100	[thread overview]
Message-ID: <56DFF594.8030603@posteo.de> (raw)
In-Reply-To: <56DFF4D2.4000708@parrot.com>

Am 2016-03-09 um 11:02 schrieb Gregor Boirie:
> Hi Daniel,
> 
> On 03/08/2016 10:16 PM, Daniel Baluta wrote:
>> On Tue, Mar 8, 2016 at 8:00 PM, Gregor Boirie
>> <gregor.boirie@parrot.com> wrote:
>>> When not compiled-in, regulator layer will return a NULL pointer when
>>> trying to get a reference to any regulator using
>>> devm_regulator_get().  As
>>> IS_ERR() does not consider this an error, the ms5611 probing
>>> operation will
>>> try to enable a NULL regulator, which will invariably cause a kernel
>>> crash.
>>> This patch fixes this situation by using devm_regulator_get_optional()
>>> instead of devm_regulator_get().
>>>
>>> Signed-off-by: Gregor Boirie <gregor.boirie@parrot.com>
>> $Subject should be here. And the commit subject should be something
>> more appropriate like:
>>
>> iio: pressure: ms5611: Fix crash when ...
> I'm a bit lost here since when Jonathan asked for "a fixes tag" inclusion
> (http://permalink.gmane.org/gmane.linux.kernel.iio/22425), I supposed he
> meant a tag such as one described in the Documentation/SubmittingPatches
> file.
> My initial attempt was sent with the subject:
> "iio:pressure:ms5611: fix oops when probing regulator".
> 
> Would you please be kind enough to give me some sort of rules as to when
> and how
> to write subject lines related to fixes patch ?
> 

I guess you can just put in a "Fixes:" line, along with your
"Signed-off-by:" lines.

> Regards,
> Grégor.
> 
>>
>>
>>> ---
>>>   drivers/iio/pressure/ms5611_core.c | 8 ++++++--
>>>   1 file changed, 6 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/iio/pressure/ms5611_core.c
>>> b/drivers/iio/pressure/ms5611_core.c
>>> index 37dbc04..a2a871b 100644
>>> --- a/drivers/iio/pressure/ms5611_core.c
>>> +++ b/drivers/iio/pressure/ms5611_core.c
>>> @@ -387,8 +387,8 @@ static const struct iio_info ms5611_info = {
>>>   static int ms5611_init(struct iio_dev *indio_dev)
>>>   {
>>>          int ret;
>>> -       struct regulator *vdd =
>>> devm_regulator_get(indio_dev->dev.parent,
>>> -                                                  "vdd");
>>> +       struct regulator *vdd =
>>> +               devm_regulator_get_optional(indio_dev->dev.parent,
>>> "vdd");
>>>
>>>          /* Enable attached regulator if any. */
>>>          if (!IS_ERR(vdd)) {
>>> @@ -398,6 +398,10 @@ static int ms5611_init(struct iio_dev *indio_dev)
>>>                                  "failed to enable Vdd supply: %d\n",
>>> ret);
>>>                          return ret;
>>>                  }
>>> +       } else {
>>> +               ret = PTR_ERR(vdd);
>>> +               if (ret != -ENODEV)
>>> +                       return ret;
>>>          }
>>>
>>>          ret = ms5611_reset(indio_dev);
>>> -- 
>>> 2.1.4
>>>
>>> -- 
>>> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> -- 
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2016-03-09 10:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08 18:00 [PATCH v5 0/1] iio:pressure:ms5611: fix and enhancements Gregor Boirie
2016-03-08 18:00 ` [PATCH v5 1/1] Fixes: 3145229f9191 ("iio:pressure:ms5611: power regulator support") Gregor Boirie
2016-03-08 21:16   ` Daniel Baluta
2016-03-09 10:02     ` Gregor Boirie
2016-03-09 10:06       ` Martin Kepplinger [this message]
2016-03-09 11:20         ` Gregor Boirie
2016-03-09 11:44           ` Daniel Baluta

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=56DFF594.8030603@posteo.de \
    --to=martink@posteo.de \
    --cc=daniel.baluta@intel.com \
    --cc=gregor.boirie@parrot.com \
    --cc=linux-iio@vger.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 NNTP newsgroup(s).