Linux USB
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Lars Gunnarsson <gunnarsson.lars@gmail.com>,
	Valentina Manea <valentina.manea.m@gmail.com>,
	Shuah Khan <shuah@kernel.org>,
	linux-usb@vger.kernel.org, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v1 1/4] tools/usbip: update documentation
Date: Fri, 19 Nov 2021 12:00:42 -0700	[thread overview]
Message-ID: <ffecc1ad-2df3-9e9d-6001-b910c82d328c@linuxfoundation.org> (raw)
In-Reply-To: <20211107171514.GA14492@dell-precision-T3610>

On 11/7/21 10:15 AM, Lars Gunnarsson wrote:
> This patch contains usbip protocol documentation updates for
> the implementation changes in subsequent patches.
> 
> Signed-off-by: Lars Gunnarsson <gunnarsson.lars@gmail.com>
> ---
> v1: New patch added in series.
> 
>   Documentation/usb/usbip_protocol.rst | 61 ++++++++++++++++++++++++----
>   1 file changed, 53 insertions(+), 8 deletions(-)
> 
> diff --git a/Documentation/usb/usbip_protocol.rst b/Documentation/usb/usbip_protocol.rst
> index 0b8541fda4d8..1afe6d297efc 100644
> --- a/Documentation/usb/usbip_protocol.rst
> +++ b/Documentation/usb/usbip_protocol.rst
> @@ -9,6 +9,11 @@ The USB/IP protocol follows a server/client architecture. The server exports the
>   USB devices and the clients import them. The device driver for the exported
>   USB device runs on the client machine.
>   
> +Initially the server may choose to export any of its available USB devices,
> +based on the busid. The device will remain exported until it's unplugged or
> +unbound from the usbip driver. It is also possible to persistently export
> +devices on a given bus by monitor when they are plugged in.
> +

The current description is mixing export and unbound.
Let's rephrase this as follows.

"The server may choose to export any of its available USB devices based on their
busid. These devices will remain exported until they are unplugged or unexported.
Optionally, it is possible to persistently export the devices on a given bus by
monitor when they are plugged in"

I don't see tools/usb/usbip/doc updated to reflect the new commands? Please
include tools/usb/usbip/doc to both usbipd.8 and usbip.8 to describe how this
new feature can be used. Also include details on how to reverse persistent
export. Right now it is a decision made on each boot and there is no need to
be concerned about exporting devices that should no longer be exported. With
this feature, it becomes important to make sure there is clear indication that
devices are being exported in persistent manner.

I would like to see the doc updates - please add them as the second patch in
this series, so it would be easier for people to review.

thanks,
-- Shuah

      reply	other threads:[~2021-11-19 19:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-07 17:15 [PATCH v1 1/4] tools/usbip: update documentation Lars Gunnarsson
2021-11-19 19:00 ` Shuah Khan [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=ffecc1ad-2df3-9e9d-6001-b910c82d328c@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=gunnarsson.lars@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=valentina.manea.m@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox