From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: arnd@arndb.de, jasowang@redhat.com, stefanha@redhat.com,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vhost: silence an unused-variable warning
Date: Sat, 9 Mar 2019 18:19:07 -0500 [thread overview]
Message-ID: <20190309181754-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20190308.151726.1373226353046701716.davem@davemloft.net>
On Fri, Mar 08, 2019 at 03:17:26PM -0800, David Miller wrote:
> From: Arnd Bergmann <arnd@arndb.de>
> Date: Wed, 6 Mar 2019 12:05:49 +0100
>
> > On some architectures, the MMU can be disabled, leading to access_ok()
> > becoming an empty macro that does not evaluate its size argument,
> > which in turn produces an unused-variable warning:
> >
> > drivers/vhost/vhost.c:1191:9: error: unused variable 's' [-Werror,-Wunused-variable]
> > size_t s = vhost_has_feature(vq, VIRTIO_RING_F_EVENT_IDX) ? 2 : 0;
> >
> > Mark the variable as __maybe_unused to shut up that warning.
> >
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>
> I'll apply this, thanks Arnd.
I queued this for next linux already and it's been in linux-next
for a while. Sorry that I didn't reply, will try to remember to do it
next time.
next prev parent reply other threads:[~2019-03-09 23:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 11:05 [PATCH] vhost: silence an unused-variable warning Arnd Bergmann
2019-03-07 3:00 ` Jason Wang
2019-03-07 3:00 ` Jason Wang
2019-03-08 23:17 ` David Miller
2019-03-09 23:19 ` Michael S. Tsirkin
2019-03-09 23:19 ` Michael S. Tsirkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-06 11:05 Arnd Bergmann
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=20190309181754-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stefanha@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.