[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAPcyv4joSgj7ok4DfW3tWQGavRDP8kp7oQRH8DgkG=0eWgNn1g@mail.gmail.com>
Date: Tue, 16 Jul 2019 20:02:00 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: "Michael S. Tsirkin" <mst@...hat.com>
Cc: Pankaj Gupta <pagupta@...hat.com>, lcapitulino@...hat.com,
virtualization@...ts.linux-foundation.org,
linux-nvdimm <linux-nvdimm@...ts.01.org>,
Cornelia Huck <cohuck@...hat.com>,
yuval shaia <yuval.shaia@...cle.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3] virtio_pmem: fix sparse warning
On Fri, Jul 12, 2019 at 7:11 AM Michael S. Tsirkin <mst@...hat.com> wrote:
>
> On Fri, Jul 12, 2019 at 10:46:10AM +0530, Pankaj Gupta wrote:
> > This patch fixes below sparse warning related to __virtio
> > type in virtio pmem driver. This is reported by Intel test
> > bot on linux-next tree.
> >
> > nd_virtio.c:56:28: warning: incorrect type in assignment
> > (different base types)
> > nd_virtio.c:56:28: expected unsigned int [unsigned] [usertype] type
> > nd_virtio.c:56:28: got restricted __virtio32
> > nd_virtio.c:93:59: warning: incorrect type in argument 2
> > (different base types)
> > nd_virtio.c:93:59: expected restricted __virtio32 [usertype] val
> > nd_virtio.c:93:59: got unsigned int [unsigned] [usertype] ret
> >
> > Reported-by: kbuild test robot <lkp@...el.com>
> > Signed-off-by: Pankaj Gupta <pagupta@...hat.com>
>
> Acked-by: Michael S. Tsirkin <mst@...hat.com>
>
> Pls merge - I assume nvdimm tree?
Yes, I'll push this with the rest to Linus tomorrow morning.
Powered by blists - more mailing lists