diff options
| author | rusty <rusty@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652> | 2014-02-12 03:17:11 +0000 |
|---|---|---|
| committer | rusty <rusty@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652> | 2014-02-12 03:17:11 +0000 |
| commit | ad640ee757d06e7f2e6b6bfb75e2087639419424 (patch) | |
| tree | 0204f5f943f1946d466f71292f497ab0d0030b07 /makepdf.sh | |
| parent | 86e2b45812fea4fbf34f6e1ee45d06d4ae886d8e (diff) | |
PCI: consistent device/PCI configuration space
Re section:
4.1.3.4 Notification of Device Configuration Changes
Feedback:
Please use "PCI configuration space" and "device configuration
state" consistently, without abbreviation. For example, from the
first sentence it looks like "device configuration state" can be
changed, but the first bullet claims it's "configuration space".
So, which one? Does "configuration space" mean "PCI configuration
space" or is it a synonym for "device configuration state"?
Because those are two different things; the driver needs to know
what exactly to rescan.
As per minutes:
https://lists.oasis-open.org/archives/virtio/201402/msg00121.html
Cc: Arun Subbarao <asubbarao@lnxw.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Rusty Russell <rusty@au1.ibm.com>
git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@240 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
Diffstat (limited to 'makepdf.sh')
0 files changed, 0 insertions, 0 deletions