All of lore.kernel.org
 help / color / mirror / Atom feed
From: refactormyself@gmail.com
To: helgaas@kernel.org
Cc: Bolarinwa Olayemi Saheed <refactormyself@gmail.com>,
	bjorn@helgaas.com, yangyicong@hisilicon.com,
	skhan@linuxfoundation.org, linux-pci@vger.kernel.org
Subject: [PATCH RFC 0/2] pci: Make return value of pcie_capability_*() consistent
Date: Mon,  4 May 2020 07:18:10 +0200	[thread overview]
Message-ID: <20200504051812.22662-1-refactormyself@gmail.com> (raw)

From: Bolarinwa Olayemi Saheed <refactormyself@gmail.com>

Changes in version 5:
 - Extend consitency to all accesors, they all now return PCIBIOS_* error
   codes
 - Enforce -ve error code, any case of > 0 error code is return as -ERANGE
   this is done in line with the implementation of pcibios_err_to_errno()
   which is now deprecated.
 - Set all PCIBIOS_* error codes to generic error codes.
 - pcibios_err_to_errno() is now dormant and deprecated. It will return
   -ERANGE if a any positive error code is passed into it.
 - Remove verbose dependency audit report from commit log. No conflict was
   discovered so far.

Changes in version 4:
 - make patch independent of earlier versions
 - add commit log
 - add justificaation and report on audit of affected functions

Bolarinwa Olayemi Saheed (2):
  pci: Make return value of pcie_capability_{read|write}_*() consistent
  Set all PCIBIOS_* error codes to generic error codes

 drivers/pci/access.c | 64 +++++++++++++++++++++++++++++++++++---------
 include/linux/pci.h  | 31 +++++++++++----------
 2 files changed, 66 insertions(+), 29 deletions(-)

-- 
2.18.2


             reply	other threads:[~2020-05-04  6:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-04  5:18 refactormyself [this message]
2020-05-04  5:18 ` [PATCH RFC 1/2] pci: Make return value of pcie_capability_*() consistent refactormyself
2020-05-05  0:06   ` Bjorn Helgaas
2020-05-04  5:18 ` [PATCH RFC 2/2] pci: Set all PCIBIOS_* error codes to generic error codes refactormyself

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=20200504051812.22662-1-refactormyself@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.