Page MenuHomeFreeBSD
Differential D54487

linuxkpi: Define `PCI_POSSIBLE_ERROR()` macro
ClosedPublic
Actions

Authored by dumbbell on Jan 4 2026, 10:17 AM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Apr 15, 12:34 PM
Unknown Object (File)
Wed, Apr 15, 12:27 PM
Unknown Object (File)
Wed, Apr 15, 7:59 AM
Unknown Object (File)
Mon, Apr 13, 6:42 PM
Unknown Object (File)
Sun, Apr 12, 7:28 PM
Unknown Object (File)
Sat, Apr 11, 2:28 PM
Unknown Object (File)
Sun, Apr 5, 8:08 AM
Unknown Object (File)
Sun, Apr 5, 5:08 AM
View All 30 Files
Subscribers
emaste
imp

Details

Reviewers
emaste
Group Reviewers
linuxkpi
Commits
rGde8bc3aad7f1: linuxkpi: Define `PCI_POSSIBLE_ERROR()` macro
rGace666bd21a2: linuxkpi: Define `PCI_POSSIBLE_ERROR()` macro
Summary

It comes with PCI_ERROR_RESPONSE and PCI_SET_ERROR_RESPONSE() but we don't use them so far. Therefore PCI_POSSIBLE_ERROR() will always reture false.

As written in the comment, this macro is a bit weird given the Linux `pci_read_*() functions can return an error code separately from the read value.

The PCI_POSSIBLE_ERROR() macro started to be used by the amdgpu DRM driver in Linux 6.10.

This is part of the update of DRM drivers to Linux 6.10.

Sponsored by: The FreeBSD Foundation

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Revision Contents
Changeset List

PathSize
sys/
compat/
linuxkpi/
common/
include/
linux/
14 lines

Diff 169109

View Options

sys/compat/linuxkpi/common/include/linux/pci.h

Loading...