From: Jason Gunthorpe <jgg@nvidia.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, kvm@vger.kernel.org,
Kirti Wankhede <kwankhede@nvidia.com>,
Max Gurtovoy <mgurtovoy@nvidia.com>,
Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
Yishai Hadas <yishaih@nvidia.com>
Subject: Re: [PATCH RFC v2] vfio: Documentation for the migration region
Date: Mon, 6 Dec 2021 15:19:33 -0400 [thread overview]
Message-ID: <20211206191933.GM4670@nvidia.com> (raw)
In-Reply-To: <87tufltxp0.fsf@redhat.com>
On Mon, Dec 06, 2021 at 07:06:35PM +0100, Cornelia Huck wrote:
> We're discussing a complex topic here, and we really don't want to
> perpetuate an unclear uAPI. This is where my push for more precise
> statements is coming from.
I appreciate that, and I think we've made a big effort toward that
direction.
Can we have some crisp feedback which statements need SHOULD/MUST/MUST
NOT and come to something?
The world needs to move forward, we can't debate this endlessly
forever. It is already another 6 weeks past since the last mlx5 driver
posting.
I don't feel like this is really converging, you two are the
maintainers, can you please drive to something acceptable, whatever it
is?
Jason
next prev parent reply other threads:[~2021-12-06 19:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 14:45 [PATCH RFC v2] vfio: Documentation for the migration region Jason Gunthorpe
2021-11-30 17:26 ` Alex Williamson
2021-11-30 18:59 ` Jason Gunthorpe
2021-11-30 22:35 ` Alex Williamson
2021-12-01 3:14 ` Jason Gunthorpe
2021-12-01 9:54 ` Shameerali Kolothum Thodi
2021-12-01 13:49 ` Jason Gunthorpe
2021-12-01 20:03 ` Alex Williamson
2021-12-01 23:25 ` Jason Gunthorpe
2021-12-02 17:05 ` Cornelia Huck
2021-12-02 17:41 ` Jason Gunthorpe
2021-12-02 17:46 ` Cornelia Huck
2021-12-03 18:06 ` Alex Williamson
2021-12-06 16:03 ` Cornelia Huck
2021-12-06 17:34 ` Jason Gunthorpe
2021-12-06 18:06 ` Cornelia Huck
2021-12-06 19:19 ` Jason Gunthorpe [this message]
2021-12-07 11:16 ` Cornelia Huck
2021-12-07 15:51 ` Jason Gunthorpe
2021-12-07 16:30 ` Cornelia Huck
2021-12-07 17:00 ` Jason Gunthorpe
2021-12-08 16:06 ` Alex Williamson
2021-12-08 20:27 ` Jason Gunthorpe
2021-12-06 19:15 ` Jason Gunthorpe
2021-12-07 10:50 ` Cornelia Huck
2021-12-07 15:37 ` Jason Gunthorpe
2021-12-07 15:56 ` Cornelia Huck
2021-12-07 16:13 ` Jason Gunthorpe
2021-12-07 16:22 ` Alex Williamson
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=20211206191933.GM4670@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=corbet@lwn.net \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=mgurtovoy@nvidia.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=yishaih@nvidia.com \
/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.