| commit | 5ef5475868d00f506699712c1569f10eaa7534a6 | |
| author | Halil Pasic <pasic@linux.vnet.ibm.com> | |
| Thu, 14 Sep 2017 10:55:35 +0000 (14 12:55 +0200) | ||
| committer | Cornelia Huck <cohuck@redhat.com> | |
| Tue, 19 Sep 2017 16:31:32 +0000 (19 18:31 +0200) | ||
| tree | 80341389871be00b62ecaade612acee6ab483737 | treesnapshot (tar.gz zip) |
| parent | a1422723f75a8b73f952fc0d7b38a702ed97e5e0 | commitdiff |
virtio-ccw: remove stale comments on endianness
We have two stale comments suggesting one should think about virtio
config space endianness a bit longer. We have just done that, and came to
the conclusion we are fine as is: it's the responsibility of the virtio
device and not of the transport (and that is how it works now). Putting
the responsibility into the transport isn't even possible, because the
transport would have to know about the config space layout of each
device.
Let us remove the stale comments.
Signed-off-by: Halil Pasic <pasic@linux.vnet.ibm.com>
Suggested-by: Cornelia Huck <cohuck@redhat.com>
Message-Id: <20170914105535.47941-1-pasic@linux.vnet.ibm.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
We have two stale comments suggesting one should think about virtio
config space endianness a bit longer. We have just done that, and came to
the conclusion we are fine as is: it's the responsibility of the virtio
device and not of the transport (and that is how it works now). Putting
the responsibility into the transport isn't even possible, because the
transport would have to know about the config space layout of each
device.
Let us remove the stale comments.
Signed-off-by: Halil Pasic <pasic@linux.vnet.ibm.com>
Suggested-by: Cornelia Huck <cohuck@redhat.com>
Message-Id: <20170914105535.47941-1-pasic@linux.vnet.ibm.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
| hw/s390x/virtio-ccw.c | diffblobblamehistory |