From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
"Enrico Weigelt, metux IT consult" <info@metux.net>,
Viresh Kumar <vireshk@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Jason Wang <jasowang@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
kernel test robot <lkp@intel.com>,
linux-gpio <linux-gpio@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] gpio: virtio: Fix sparse warnings
Date: Tue, 31 Aug 2021 11:07:28 +0200 [thread overview]
Message-ID: <CAMpxmJWeYTf4yVTJmnHf8Lqrf=J9rGxq54rPFGMYjLaKhH6fdA@mail.gmail.com> (raw)
In-Reply-To: <20210831063149.gcctzqtn635mn3wb@vireshk-i7>
On Tue, Aug 31, 2021 at 8:31 AM Viresh Kumar <viresh.kumar@linaro.org> wrote:
>
> 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@intel.com>
> > > Fixes: 3a29355a22c0 ("gpio: Add virtio-gpio driver")
> > > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> >
> > Acked-by: Michael S. Tsirkin <mst@redhat.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.
I just applied it on top of my for-next branch.
Bart
>
> > Also, the driver lacks a MAINTAINERS entry - we want at least
> > L: virtualization@lists.linux-foundation.org
> > on all virtio drivers.
>
> Sure, I will send a patch for that.
>
> --
> viresh
prev parent reply other threads:[~2021-08-31 9:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 5:29 [PATCH] gpio: virtio: Fix sparse warnings Viresh Kumar
2021-08-31 6:25 ` Michael S. Tsirkin
2021-08-31 6:31 ` Viresh Kumar
2021-08-31 9:07 ` Bartosz Golaszewski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMpxmJWeYTf4yVTJmnHf8Lqrf=J9rGxq54rPFGMYjLaKhH6fdA@mail.gmail.com' \
--to=bgolaszewski@baylibre.com \
--cc=info@metux.net \
--cc=jasowang@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mst@redhat.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=vireshk@kernel.org \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).