From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: "Gustavo A. R. Silva" <garsilva@embeddedor.com>,
Tejun Heo <tj@kernel.org>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sata_rcar: fix error return code in sata_rcar_probe()
Date: Fri, 30 Jun 2017 23:03:05 +0300 [thread overview]
Message-ID: <e7f03776-d0d7-d007-57c9-df75822e73be@cogentembedded.com> (raw)
In-Reply-To: <20170630144633.Horde.7_6XB0hRnIIuucUlRN2ico3@gator4166.hostgator.com>
On 06/30/2017 10:46 PM, Gustavo A. R. Silva wrote:
>>>>> Print error message and propagate the return value of
>>>>> platform_get_irq on failure.
>>>>
>>>> You should have probably mentioned that this function no longer returns 0
>>>> on error.
>>>
>>> Yeah, the patches looks good to me but I'd really appreciate more
>>> context in the changelogs. Gustavo, can you please respin the
>>> patches?
>>>
>>
>> Absolutely.
>>
>> What do you think about the following changelog:
>>
>> platform_get_irq() returns an error code, but the sata_rcar driver
>> ignores it and always returns -EINVAL. This is not correct, and
>> prevents -EPROBE_DEFER from being propagated properly.
>>
>> Print error message and propagate the return value of platform_get_irq
>> on failure. Also, with this change function sata_rcar_probe() no longer
>> returns 0 on error.
>>
>
> Errata, this would be final the chagelog:
>
> platform_get_irq() returns an error code, but the sata_rcar driver
> ignores it and always returns -EINVAL. This is not correct, and
> prevents -EPROBE_DEFER from being propagated properly. Also,
> notice that platform_get_irq() no longer returns 0 on error.
>
> Print error message and propagate the return value of platform_get_irq
> on failure.
Now I'm OK with that.
> Thanks
MBR, Sergei
next prev parent reply other threads:[~2017-06-30 20:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 5:22 Gustavo A. R. Silva
2017-06-30 9:42 ` Sergei Shtylyov
2017-06-30 12:01 ` Tejun Heo
2017-06-30 19:36 ` Gustavo A. R. Silva
2017-06-30 19:42 ` Sergei Shtylyov
2017-06-30 19:54 ` Gustavo A. R. Silva
2017-06-30 19:46 ` Gustavo A. R. Silva
2017-06-30 20:03 ` Sergei Shtylyov [this message]
2017-06-30 20:34 ` Gustavo A. R. Silva
2017-06-30 21:08 ` [PATCH v2] " Gustavo A. R. Silva
2017-06-30 21:09 ` Sergei Shtylyov
2017-06-30 21:11 ` Gustavo A. R. Silva
2017-06-30 12:35 ` [PATCH] " Sergei Shtylyov
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=e7f03776-d0d7-d007-57c9-df75822e73be@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=garsilva@embeddedor.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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®