| Message ID | 20220905124746.1975-2-jgross@suse.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | tools/xenstore: add some new features to the documentation | expand |
Hi Juergen, On 05/09/2022 13:47, Juergen Gross wrote: > Drop mentioning the non-existent read-only socket in the migration > stream description document. > > The related record field was removed in commit 8868a0e3f674 ("docs: > update the xenstore migration stream documentation). > > Signed-off-by: Juergen Gross <jgross@suse.com> Acked-by: Julien Grall <jgrall@amazon.com> I think this also want to be backported so the documentation is accurate on older release. Cheers,
diff --git a/docs/designs/xenstore-migration.md b/docs/designs/xenstore-migration.md index b94af7fd7c..efa526f420 100644 --- a/docs/designs/xenstore-migration.md +++ b/docs/designs/xenstore-migration.md @@ -129,11 +129,9 @@ xenstored state that needs to be restored. | `evtchn-fd` | The file descriptor used to communicate with | | | the event channel driver | -xenstored will resume in the original process context. Hence `rw-socket-fd` and -`ro-socket-fd` simply specify the file descriptors of the sockets. Sockets -are not always used, however, and so -1 will be used to denote an unused -socket. - +xenstored will resume in the original process context. Hence `rw-socket-fd` +simply specifies the file descriptor of the socket. Sockets are not always +used, however, and so -1 will be used to denote an unused socket. \pagebreak
Drop mentioning the non-existent read-only socket in the migration stream description document. The related record field was removed in commit 8868a0e3f674 ("docs: update the xenstore migration stream documentation). Signed-off-by: Juergen Gross <jgross@suse.com> --- V3: - new patch --- docs/designs/xenstore-migration.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-)