From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Gonglei (Arei)" <arei.gonglei@huawei.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH 0/2] virtio: fix complaint by sparse
Date: Sun, 27 Nov 2016 04:53:07 +0200 [thread overview]
Message-ID: <20161127045247-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <33183CC9F5247A488A2544077AF19020D979FA1E@SZXEMA503-MBS.china.huawei.com>
this is in my tree, will be in the next pull request.
On Sat, Nov 26, 2016 at 09:36:50AM +0000, Gonglei (Arei) wrote:
> Ping...?
>
> > -----Original Message-----
> > From: Gonglei (Arei)
> > Sent: Tuesday, November 22, 2016 1:52 PM
> > To: virtualization@lists.linux-foundation.org; linux-kernel@vger.kernel.org
> > Cc: mst@redhat.com; jasowang@redhat.com; Gonglei (Arei)
> > Subject: [PATCH 0/2] virtio: fix complaint by sparse
> >
> > I found some warnings reported by sparse in the virtio code
> > when I checked virtio-crypto's driver stuff. Let's fix them.
> >
> > Gonglei (2):
> > virtio_pci_modern: fix complaint by sparse
> > virtio_ring: fix complaint by sparse
> >
> > drivers/virtio/virtio_pci_modern.c | 8 ++++----
> > drivers/virtio/virtio_ring.c | 4 ++--
> > 2 files changed, 6 insertions(+), 6 deletions(-)
> >
> > --
> > 1.8.3.1
> >
prev parent reply other threads:[~2016-11-27 2:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 5:51 [PATCH 0/2] virtio: fix complaint by sparse Gonglei
2016-11-22 5:51 ` [PATCH 1/2] virtio_pci_modern: " Gonglei
2016-11-22 5:51 ` [PATCH 2/2] virtio_ring: " Gonglei
2016-11-22 15:04 ` Michael S. Tsirkin
[not found] ` <20161122170346-mutt-send-email-mst@kernel.org>
2016-11-22 15:16 ` Thomas Huth
2016-11-22 17:25 ` Andy Lutomirski
2016-11-22 17:50 ` Cornelia Huck
2016-11-26 9:36 ` [PATCH 0/2] virtio: " Gonglei (Arei)
2016-11-27 2:53 ` Michael S. Tsirkin [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=20161127045247-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=linux-kernel@vger.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).