Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: 412574090@163.com
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org, xiongxin@kylinos.cn,
	weiyufeng <weiyufeng@kylinos.cn>
Subject: Re: [PATCH] PCI/ERR: Use PCI_POSSIBLE_ERROR() to check config reads
Date: Tue, 6 Aug 2024 14:17:54 -0500	[thread overview]
Message-ID: <20240806191754.GA73658@bhelgaas> (raw)
In-Reply-To: <20240806065050.28725-1-412574090@163.com>

On Tue, Aug 06, 2024 at 02:50:50PM +0800, 412574090@163.com wrote:
> From: weiyufeng <weiyufeng@kylinos.cn>
> 
> Use PCI_POSSIBLE_ERROR() to check the response we get when we read data
> from hardware.  This unifies PCI error response checking and makes error
> checks consistent and easier to find.
> 
> Signed-off-by: weiyufeng <weiyufeng@kylinos.cn>

Thanks, applied to pci/hotplug for v6.12.

> ---
>  drivers/pci/hotplug/cpqphp_pci.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/pci/hotplug/cpqphp_pci.c b/drivers/pci/hotplug/cpqphp_pci.c
> index e9f1fb333a71..718bc6cf12cb 100644
> --- a/drivers/pci/hotplug/cpqphp_pci.c
> +++ b/drivers/pci/hotplug/cpqphp_pci.c
> @@ -138,7 +138,7 @@ static int PCI_RefinedAccessConfig(struct pci_bus *bus, unsigned int devfn, u8 o
>  
>  	if (pci_bus_read_config_dword(bus, devfn, PCI_VENDOR_ID, &vendID) == -1)
>  		return -1;
> -	if (vendID == 0xffffffff)
> +	if (PCI_POSSIBLE_ERROR(vendID))
>  		return -1;
>  	return pci_bus_read_config_dword(bus, devfn, offset, value);
>  }
> @@ -253,7 +253,7 @@ static int PCI_GetBusDevHelper(struct controller *ctrl, u8 *bus_num, u8 *dev_num
>  			*dev_num = tdevice;
>  			ctrl->pci_bus->number = tbus;
>  			pci_bus_read_config_dword(ctrl->pci_bus, *dev_num, PCI_VENDOR_ID, &work);
> -			if (!nobridge || (work == 0xffffffff))
> +			if (!nobridge || PCI_POSSIBLE_ERROR(work))
>  				return 0;
>  
>  			dbg("bus_num %d devfn %d\n", *bus_num, *dev_num);
> -- 
> 2.25.1
> 

      reply	other threads:[~2024-08-06 19:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-06  6:50 [PATCH] PCI/ERR: Use PCI_POSSIBLE_ERROR() to check config reads 412574090
2024-08-06 19:17 ` Bjorn Helgaas [this message]

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=20240806191754.GA73658@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=412574090@163.com \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=weiyufeng@kylinos.cn \
    --cc=xiongxin@kylinos.cn \
    /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