vpc: fix beX_to_cpu() and cpu_to_beX() confusion
commita4127c428e61317b2966ec7fe480c3c6fb2d08df
authorStefan Hajnoczi <stefanha@redhat.com>
Tue, 23 Sep 2014 09:40:55 +0000 (23 10:40 +0100)
committerKevin Wolf <kwolf@redhat.com>
Thu, 25 Sep 2014 13:24:14 +0000 (25 15:24 +0200)
treee0d2d0e3f5924442fcdb426b3d3db0a59788c34a
parentf9d7b4b3b4249336be665180a1aea7ce5497d2ca
vpc: fix beX_to_cpu() and cpu_to_beX() confusion

The beX_to_cpu() and cpu_to_beX() functions perform the same operation -
they do a byteswap if the host CPU endianness is little-endian or a
nothing otherwise.

The point of two names for the same operation is that it documents which
direction the data is being converted.  This makes it clear whether the
data is suitable for CPU processing or in its external representation.

This patch fixes incorrect beX_to_cpu()/cpu_to_beX() usage.

Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
block/vpc.c