From: Viresh Kumar <viresh.kumar@linaro.org>
To: Wolfram Sang <wsa@kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Vincent Whitchurch <vincent.whitchurch@axis.com>,
jie.deng@intel.com, conghui.chen@intel.com,
virtualization@lists.linux-foundation.org,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@axis.com
Subject: Re: [PATCH v2 0/2] virtio-i2c: Fix buffer handling
Date: Thu, 25 Nov 2021 12:17:50 +0530 [thread overview]
Message-ID: <20211125064750.ywq3vd76uy2levoz@vireshk-i7> (raw)
In-Reply-To: <YZ8rxHDPo68AT4HN@kunai>
On 25-11-21, 07:24, Wolfram Sang wrote:
>
> > Wolfram, you can apply that one as well, it looks okay.
>
> Is it? I read that the code only waits for the last request while
> Michael suggested to wait for all of them? And he did not ack patch 2
> while he acked patch 1. Did I misunderstand?
Okay, I misread it then.
To clarify, we should initialize the completion for each buffer and
wait for all of them to be completed before returning back to the
user.
Lets wait for an update by Vincent for that then.
--
viresh
prev parent reply other threads:[~2021-11-25 6:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 16:04 [PATCH v2 0/2] virtio-i2c: Fix buffer handling Vincent Whitchurch
2021-11-11 16:04 ` [PATCH v2 1/2] i2c: virtio: disable timeout handling Vincent Whitchurch
2021-11-11 16:46 ` Michael S. Tsirkin
2021-11-12 2:35 ` Viresh Kumar
2021-11-19 15:30 ` Vincent Whitchurch
2021-11-23 9:52 ` Wolfram Sang
2021-11-23 9:54 ` Viresh Kumar
2021-11-23 9:55 ` Wolfram Sang
2021-11-11 16:04 ` [PATCH v2 2/2] i2c: virtio: fix completion handling Vincent Whitchurch
2021-11-11 16:57 ` Michael S. Tsirkin
2021-12-02 15:34 ` Vincent Whitchurch
2021-11-24 23:55 ` [PATCH v2 0/2] virtio-i2c: Fix buffer handling Michael S. Tsirkin
2021-11-25 3:21 ` Viresh Kumar
2021-11-25 6:24 ` Wolfram Sang
2021-11-25 6:47 ` Viresh Kumar [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=20211125064750.ywq3vd76uy2levoz@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=conghui.chen@intel.com \
--cc=jie.deng@intel.com \
--cc=kernel@axis.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=vincent.whitchurch@axis.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=wsa@kernel.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).