From: "Michael S. Tsirkin" <mst@redhat.com>
To: Si-Wei Liu <si-wei.liu@oracle.com>
Cc: lvivier@redhat.com, llvm@lists.linux.dev,
virtualization@lists.linux-foundation.org,
Nathan Chancellor <nathan@kernel.org>,
eperezma@redhat.com, Eli Cohen <elic@nvidia.com>
Subject: Re: [PATCH v7 07/14] vdpa/mlx5: Support configuring max data virtqueue
Date: Mon, 10 Jan 2022 01:53:04 -0500 [thread overview]
Message-ID: <20220110015040-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <233b923b-e6e2-0d47-8230-df91a35ee4de@oracle.com>
On Fri, Jan 07, 2022 at 05:43:15PM -0800, Si-Wei Liu wrote:
> It's unfortunate. Don't know why this series got pulled into linux-next
> prematurely. The code review is still on going and there were outstanding
> comments that hadn't been addressed yet.
Most patches got acked, and the merge window is closing.
The only couple of issues seem to be with this specific patch, and I
think I fixed them up.
Still - I can hold them if necessary. What do others think?
--
MST
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2022-01-10 6:53 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220105114646.577224-1-elic@nvidia.com>
[not found] ` <20220105114646.577224-4-elic@nvidia.com>
2022-01-07 0:33 ` [PATCH v7 03/14] vdpa: Sync calls set/get config/status with cf_mutex Si-Wei Liu
2022-01-07 5:08 ` Jason Wang
2022-01-08 1:23 ` Si-Wei Liu
2022-01-10 6:05 ` Jason Wang
2022-01-11 1:30 ` Si-Wei Liu
2022-01-11 4:46 ` Jason Wang
2022-01-11 6:26 ` Parav Pandit via Virtualization
2022-01-11 9:15 ` Si-Wei Liu
2022-01-11 9:23 ` Si-Wei Liu
[not found] ` <20220109140956.GA70879@mtl-vdi-166.wap.labs.mlnx>
2022-01-11 1:14 ` Si-Wei Liu
[not found] ` <20220105114646.577224-6-elic@nvidia.com>
2022-01-07 1:25 ` [PATCH v7 05/14] vdpa: Allow to configure max data virtqueues Si-Wei Liu
[not found] ` <20220105114646.577224-8-elic@nvidia.com>
2022-01-07 1:27 ` [PATCH v7 07/14] vdpa/mlx5: Support configuring max data virtqueue Si-Wei Liu
2022-01-07 1:50 ` Si-Wei Liu
2022-01-07 5:43 ` Jason Wang
2022-01-08 1:38 ` Si-Wei Liu
[not found] ` <20220109141023.GB70879@mtl-vdi-166.wap.labs.mlnx>
2022-01-11 1:00 ` Si-Wei Liu
[not found] ` <20220111073416.GB149570@mtl-vdi-166.wap.labs.mlnx>
2022-01-11 8:28 ` Jason Wang
2022-01-11 12:05 ` Michael S. Tsirkin
2022-01-12 2:36 ` Jason Wang
2022-01-11 8:52 ` Si-Wei Liu
[not found] ` <20220111152154.GA165838@mtl-vdi-166.wap.labs.mlnx>
2022-01-11 15:31 ` Michael S. Tsirkin
2022-01-11 22:21 ` Si-Wei Liu
[not found] ` <YdiABvwrK3WxfHqb@archlinux-ax161>
2022-01-08 1:43 ` Si-Wei Liu
2022-01-10 6:53 ` Michael S. Tsirkin [this message]
[not found] ` <20220105114646.577224-11-elic@nvidia.com>
2022-01-07 2:12 ` [PATCH v7 10/14] vdpa: Support reporting max device capabilities Si-Wei Liu
[not found] ` <20220105114646.577224-12-elic@nvidia.com>
2022-01-07 2:12 ` [PATCH v7 11/14] vdpa/mlx5: Report " Si-Wei Liu
2022-01-07 5:49 ` Jason Wang
[not found] ` <20220105114646.577224-5-elic@nvidia.com>
2022-01-07 5:14 ` [PATCH v7 04/14] vdpa: Read device configuration only if FEATURES_OK Jason Wang
[not found] ` <20220105114646.577224-9-elic@nvidia.com>
2022-01-07 5:46 ` [PATCH v7 08/14] vdpa: Add support for returning device configuration information Jason Wang
[not found] ` <20220105114646.577224-13-elic@nvidia.com>
2022-01-07 5:50 ` [PATCH v7 12/14] vdpa/vdpa_sim: Configure max supported virtqueues Jason Wang
[not found] ` <20220105114646.577224-14-elic@nvidia.com>
2022-01-07 5:51 ` [PATCH v7 13/14] vdpa: Use BIT_ULL for bit operations Jason Wang
[not found] ` <20220105114646.577224-15-elic@nvidia.com>
2022-01-07 5:51 ` [PATCH v7 14/14] vdpa/vdpa_sim_net: Report max device capabilities Jason Wang
2022-01-10 7:04 ` [PATCH v7 00/14] Allow for configuring max number of virtqueue pairs Michael S. Tsirkin
2022-01-10 7:09 ` Jason Wang
2022-01-11 1:59 ` Si-Wei Liu
[not found] ` <20220110074958.GA105688@mtl-vdi-166.wap.labs.mlnx>
2022-01-11 2:02 ` Si-Wei Liu
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=20220110015040-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=elic@nvidia.com \
--cc=eperezma@redhat.com \
--cc=llvm@lists.linux.dev \
--cc=lvivier@redhat.com \
--cc=nathan@kernel.org \
--cc=si-wei.liu@oracle.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 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).