From: Julien Grall <julien@xen.org>
To: Jan Beulich <jbeulich@suse.com>
Cc: Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
paul@xen.org, Andrew Cooper <andrew.cooper3@citrix.com>,
Julien Grall <jgrall@amazon.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v4 for-4.14 2/2] pvcalls: Document correctly and explicitely the padding for all arches
Date: Mon, 29 Jun 2020 12:24:12 +0100 [thread overview]
Message-ID: <0c03797c-33c2-8f56-fb0e-b578712cf681@xen.org> (raw)
In-Reply-To: <37362d94-053d-5eb9-d2fa-9d30690313f0@suse.com>
On 29/06/2020 12:22, Jan Beulich wrote:
> On 29.06.2020 12:03, Julien Grall wrote:
>> On 29/06/2020 09:28, Jan Beulich wrote:
>>> On 27.06.2020 11:55, Julien Grall wrote:
>>>> As an aside, the padding sadly cannot be mandated to be 0 as they are
>>>> already present. So it is not going to be possible to use the padding
>>>> for extending a command in the future.
>>>
>>> Why is the other adjustment fine to make due to still being tech
>>> preview, but this one wouldn't be for the same reason?
>>
>> This is mostly a left-over of the previous message. Although, I am not
>> really inclined to address this myself any time soon.
>
> Sure, I didn't mean to indicate I might expect you to. But perhaps
> here the wording could be slightly changed as well?
I am planning to remove the paragraph completely.
Cheers,
--
Julien Grall
next prev parent reply other threads:[~2020-06-29 11:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-27 9:55 [PATCH v4 for-4.14 0/2] pvcalls: Reconciliate the spec and the Julien Grall
2020-06-27 9:55 ` [PATCH v4 for-4.14 1/2] pvcalls: Clearly spell out that the header is just a reference Julien Grall
2020-06-27 11:55 ` Jürgen Groß
2020-06-29 7:38 ` Paul Durrant
2020-06-27 9:55 ` [PATCH v4 for-4.14 2/2] pvcalls: Document correctly and explicitely the padding for all arches Julien Grall
2020-06-27 11:53 ` Jürgen Groß
2020-06-29 7:37 ` Paul Durrant
2020-06-29 8:28 ` Jan Beulich
2020-06-29 10:03 ` Julien Grall
2020-06-29 11:22 ` Jan Beulich
2020-06-29 11:24 ` Julien Grall [this message]
2020-06-29 15:41 ` Stefano Stabellini
2020-07-04 15:29 ` Julien Grall
2020-07-09 12:01 ` Julien Grall
2020-07-09 21:43 ` Stefano Stabellini
2020-07-10 5:44 ` Julien Grall
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=0c03797c-33c2-8f56-fb0e-b578712cf681@xen.org \
--to=julien@xen.org \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=jgrall@amazon.com \
--cc=jgross@suse.com \
--cc=paul@xen.org \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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 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.