[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200615134650.GA2030477@ziepe.ca>
Date: Mon, 15 Jun 2020 10:46:50 -0300
From: Jason Gunthorpe <jgg@...pe.ca>
To: refactormyself@...il.com
Cc: helgaas@...nel.org, bjorn@...gaas.com, skhan@...uxfoundation.org,
linux-pci@...r.kernel.org, Vinod Koul <vkoul@...nel.org>,
dmaengine@...r.kernel.org,
Mike Marciniszyn <mike.marciniszyn@...el.com>,
Dennis Dalessandro <dennis.dalessandro@...el.com>,
Doug Ledford <dledford@...hat.com>, linux-rdma@...r.kernel.org,
Don Brace <don.brace@...rosemi.com>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
esc.storagedev@...rosemi.com, linux-scsi@...r.kernel.org,
Russell Currey <ruscur@...sell.cc>,
Sam Bobroff <sbobroff@...ux.ibm.com>,
Oliver O'Halloran <oohall@...il.com>,
linuxppc-dev@...ts.ozlabs.org,
linux-kernel-mentees@...ts.linuxfoundation.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/8 v2] PCI: Align return values of PCIe capability and
PCI accessors
On Mon, Jun 15, 2020 at 09:32:17AM +0200, refactormyself@...il.com wrote:
> From: Bolarinwa Olayemi Saheed <refactormyself@...il.com>
>
>
> PATCH 1/8 to 7/8:
> PCIBIOS_ error codes have positive values and they are passed down the
> call heirarchy from accessors. For functions which are meant to return
> only a negative value on failure, passing on this value is a bug.
> To mitigate this, call pcibios_err_to_errno() before passing on return
> value from PCIe capability accessors call heirarchy. This function
> converts any positive PCIBIOS_ error codes to negative generic error
> values.
>
> PATCH 8/8:
> The PCIe capability accessors can return 0, -EINVAL, or any PCIBIOS_ error
> code. The pci accessor on the other hand can only return 0 or any PCIBIOS_
> error code.This inconsistency among these accessor makes it harder for
> callers to check for errors.
> Return PCIBIOS_BAD_REGISTER_NUMBER instead of -EINVAL in all PCIe
> capability accessors.
>
> MERGING:
> These may all be merged via the PCI tree, since it is a collection of
> similar fixes. This way they all get merged at once.
I prefer this not happen for active trees, it just risks needless
merge conflicts.
I will take the hfi1 patches at least, let me know when they are
reviewed
Thanks,
Jason
Powered by blists - more mailing lists