public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Yuan Yao <yuanyaogoog@chromium.org>
Cc: Jason Wang <jasowang@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Keiichi Watanabe <keiichiw@chromium.org>,
	Daniel Verkamp <dverkamp@chromium.org>,
	Takaya Saeki <takayas@chromium.org>,
	Junichi Uekawa <uekawa@chromium.org>,
	"David S. Miller" <davem@davemloft.net>,
	Tiwei Bie <tiwei.bie@intel.com>,
	Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] virtio_ring: fix avail_wrap_counter in virtqueue_add_packed
Date: Tue, 8 Aug 2023 05:13:31 -0400	[thread overview]
Message-ID: <20230808051304-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAOJyEHaR1Y3VsKNpLqxf-ewAEf8JJDChjmnFM_0mv=hOg+X-vA@mail.gmail.com>

On Tue, Aug 08, 2023 at 05:37:29PM +0900, Yuan Yao wrote:
> Thank you for reviewing, sent a patch with your ack.

Don't do this pls. And don't top post please.


  parent reply	other threads:[~2023-08-08 19:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-08  5:10 [PATCH] virtio_ring: fix avail_wrap_counter in virtqueue_add_packed Yuan Yao
2023-08-08  5:43 ` Jason Wang
2023-08-08  5:59   ` Michael S. Tsirkin
2023-08-08  6:05     ` Jason Wang
     [not found]   ` <CAOJyEHaXqmHStJnHrT0H4QsTJBxjBxVe+33EuWm9H3wApPKtxQ@mail.gmail.com>
2023-08-08  6:05     ` Jason Wang
     [not found]       ` <CAOJyEHaR1Y3VsKNpLqxf-ewAEf8JJDChjmnFM_0mv=hOg+X-vA@mail.gmail.com>
2023-08-08  9:13         ` Michael S. Tsirkin [this message]
     [not found]           ` <CAOJyEHYgvw7za0ksKNPu9TF1+8MwVFbctMbukgbAoQnf9da+hA@mail.gmail.com>
     [not found]             ` <CAOJyEHZs=59nZ=XTYu-mZWTz18OT7f6TknCxWksYeQZbPy2oUQ@mail.gmail.com>
2023-08-28  4:43               ` Michael S. Tsirkin
  -- strict thread matches above, loose matches on Subject: below --
2023-08-08  8:32 Yuan Yao
     [not found] ` <CAOJyEHb_KjPawwH+U30iJCDjB-VqH_FR-4qAsUk9T6Sn8FZMBQ@mail.gmail.com>
2023-08-10 19:19   ` Michael S. Tsirkin

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=20230808051304-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=davem@davemloft.net \
    --cc=dverkamp@chromium.org \
    --cc=jasowang@redhat.com \
    --cc=keiichiw@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=takayas@chromium.org \
    --cc=tiwei.bie@intel.com \
    --cc=uekawa@chromium.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xuanzhuo@linux.alibaba.com \
    --cc=yuanyaogoog@chromium.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