[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210831063149.gcctzqtn635mn3wb@vireshk-i7>
Date: Tue, 31 Aug 2021 12:01:49 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: "Michael S. Tsirkin" <mst@...hat.com>
Cc: "Enrico Weigelt, metux IT consult" <info@...ux.net>,
Viresh Kumar <vireshk@...nel.org>,
Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <bgolaszewski@...libre.com>,
Jason Wang <jasowang@...hat.com>,
Vincent Guittot <vincent.guittot@...aro.org>,
kernel test robot <lkp@...el.com>,
linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org
Subject: Re: [PATCH] gpio: virtio: Fix sparse warnings
On 31-08-21, 02:25, Michael S. Tsirkin wrote:
> On Tue, Aug 31, 2021 at 10:59:25AM +0530, Viresh Kumar wrote:
> > Fix warnings reported by sparse, related to type mismatch between u16
> > and __le16.
> >
> > Reported-by: kernel test robot <lkp@...el.com>
> > Fixes: 3a29355a22c0 ("gpio: Add virtio-gpio driver")
> > Signed-off-by: Viresh Kumar <viresh.kumar@...aro.org>
>
> Acked-by: Michael S. Tsirkin <mst@...hat.com>
>
> I'm not sure which tree has the above commit - can this be squashed?
It has gone via the GPIO tree:
https://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git/log/?h=gpio/for-next
I believe it can be squashed, Bartosz can confirm the same though.
> Also, the driver lacks a MAINTAINERS entry - we want at least
> L: virtualization@...ts.linux-foundation.org
> on all virtio drivers.
Sure, I will send a patch for that.
--
viresh
Powered by blists - more mailing lists