From: Saheed Bolarinwa <refactormyself@gmail.com>
To: Yicong Yang <yangyicong@hisilicon.com>, helgaas@kernel.org
Cc: bjorn@helgaas.com, skhan@linuxfoundation.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH] Replace -EINVAL with PCIBIOS_BAD_REGISTER_NUMBER
Date: Fri, 10 Apr 2020 18:13:11 +0200 [thread overview]
Message-ID: <7a543d6e-4c23-c9d1-7abd-0bbf4031b2c1@gmail.com> (raw)
In-Reply-To: <31a43a1a-d271-7652-db62-1a7c55cd135b@hisilicon.com>
On 4/10/20 3:28 AM, Yicong Yang wrote:
> Hi Bolarinwa,
>
> I notice some drivers use these functions and if there is an error, pass the error code
> directly to the userspace. As it's our private error code, is it appropriate to pass or
> should we call pcibios_err_to_errno()(include/linux/pci.h, line 672) to do the conversion?
Hello Yicong,
Thank you for pointing out that function to me. I have resent the patch.
Saheed
> Regards,
> Yicong
>
> On 2020/4/10 0:16, Bolarinwa Olayemi Saheed wrote:
>> Signed-off-by: Bolarinwa Olayemi Saheed <refactormyself@gmail.com>
>> Suggested-by: Bjorn Helgaas <bjorn@helgaas.com>
>> ---
>> drivers/pci/access.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/pci/access.c b/drivers/pci/access.c
>> index 79c4a2ef269a..451f2b8b2b3c 100644
>> --- a/drivers/pci/access.c
>> +++ b/drivers/pci/access.c
>> @@ -409,7 +409,7 @@ int pcie_capability_read_word(struct pci_dev *dev, int pos, u16 *val)
>>
>> *val = 0;
>> if (pos & 1)
>> - return -EINVAL;
>> + return PCIBIOS_BAD_REGISTER_NUMBER;
>>
>> if (pcie_capability_reg_implemented(dev, pos)) {
>> ret = pci_read_config_word(dev, pci_pcie_cap(dev) + pos, val);
>> @@ -444,7 +444,7 @@ int pcie_capability_read_dword(struct pci_dev *dev, int pos, u32 *val)
>>
>> *val = 0;
>> if (pos & 3)
>> - return -EINVAL;
>> + return PCIBIOS_BAD_REGISTER_NUMBER;
>>
>> if (pcie_capability_reg_implemented(dev, pos)) {
>> ret = pci_read_config_dword(dev, pci_pcie_cap(dev) + pos, val);
next prev parent reply other threads:[~2020-04-10 17:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 16:16 [PATCH] Replace -EINVAL with PCIBIOS_BAD_REGISTER_NUMBER Bolarinwa Olayemi Saheed
2020-04-10 1:28 ` Yicong Yang
2020-04-10 16:13 ` Saheed Bolarinwa [this message]
2020-04-10 20:22 ` Bjorn Helgaas
2020-04-11 2:10 ` Yicong Yang
2020-04-19 5:56 ` Saheed Bolarinwa
2020-04-24 15:17 ` Bjorn Helgaas
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=7a543d6e-4c23-c9d1-7abd-0bbf4031b2c1@gmail.com \
--to=refactormyself@gmail.com \
--cc=bjorn@helgaas.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=yangyicong@hisilicon.com \
/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).