search for: 3argfbwz

...urthermore, it means the warnings exist for all VIRTIO_1 devices because > they are definitely LE, which it's not necessary to use virtio_to_cpu/cpu_to_virtio. > > > PS: I googled a discussion about this topic for virtio-input device, pls see: > http://linux.kernel.narkive.com/3argfbWz/patch-1-1-add-virtio-input-driver > > Regards, > -Gonglei Looks like we changed the macros since - at least ATM virtio_console_config uses __u16 fields (which is probably a bug - I'll look into fixing it up) and they do not seem to trigger warnings. > > If you want it in LE f...

...urthermore, it means the warnings exist for all VIRTIO_1 devices because > they are definitely LE, which it's not necessary to use virtio_to_cpu/cpu_to_virtio. > > > PS: I googled a discussion about this topic for virtio-input device, pls see: > http://linux.kernel.narkive.com/3argfbWz/patch-1-1-add-virtio-input-driver > > Regards, > -Gonglei Looks like we changed the macros since - at least ATM virtio_console_config uses __u16 fields (which is probably a bug - I'll look into fixing it up) and they do not seem to trigger warnings. > > If you want it in LE f...

On Tue, Nov 22, 2016 at 04:10:22PM +0800, Gonglei wrote: > Virtio modern devices are always little edian, let's introduce > the LE functions for read/write configuration space for > virtio modern devices, which avoid complaint by Sparse when > we use the virtio_creaed/virtio_cwrite in VIRTIO_1 devices. > > Signed-off-by: Gonglei <arei.gonglei at huawei.com> > ---

On Tue, Nov 22, 2016 at 04:10:22PM +0800, Gonglei wrote: > Virtio modern devices are always little edian, let's introduce > the LE functions for read/write configuration space for > virtio modern devices, which avoid complaint by Sparse when > we use the virtio_creaed/virtio_cwrite in VIRTIO_1 devices. > > Signed-off-by: Gonglei <arei.gonglei at huawei.com> > ---

...virtio-crypto device. Furthermore, it means the warnings exist for all VIRTIO_1 devices because they are definitely LE, which it's not necessary to use virtio_to_cpu/cpu_to_virtio. PS: I googled a discussion about this topic for virtio-input device, pls see: http://linux.kernel.narkive.com/3argfbWz/patch-1-1-add-virtio-input-driver Regards, -Gonglei > If you want it in LE format, swap it! > > > > > -- > > 1.8.3.1 > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: virtio-dev-unsubscribe at lists.o...

...warnings exist for all VIRTIO_1 devices because > > they are definitely LE, which it's not necessary to use virtio_to_cpu/cpu_to_virtio. > > > > > > PS: I googled a discussion about this topic for virtio-input device, pls see: > > http://linux.kernel.narkive.com/3argfbWz/patch-1-1-add-virtio-input-driver > > > > Regards, > > -Gonglei > > Looks like we changed the macros since - at least ATM > virtio_console_config uses __u16 fields (which is probably a bug - > I'll look into fixing it up) and they > do not seem to trigger warn...