From: Eric Blake <eblake@redhat.com>
To: Frediano Ziglio <fziglio@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-trivial <qemu-trivial@nongnu.org>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] usb: Fix typo in documentation
Date: Wed, 7 Dec 2016 09:53:40 -0600 [thread overview]
Message-ID: <61c44ab2-01c7-4187-7a5a-6c498f70e31c@redhat.com> (raw)
In-Reply-To: <20161207123959.4565-1-fziglio@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 1341 bytes --]
On 12/07/2016 06:39 AM, Frediano Ziglio wrote:
> Signed-off-by: Frediano Ziglio <fziglio@redhat.com>
Mentioning 'simliar' in the commit message would make it easier to pick
out which word is being changed, when not using a colored-by-word diff.
This patch can also go through qemu-trivial (cc'd).
Reviewed-by: Eric Blake <eblake@redhat.com>
> ---
> docs/usb-storage.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/docs/usb-storage.txt b/docs/usb-storage.txt
> index fbc1f2e..551af6f 100644
> --- a/docs/usb-storage.txt
> +++ b/docs/usb-storage.txt
> @@ -34,7 +34,7 @@ with tree logical units:
> Number three emulates the classic bulk-only transport protocol too.
> It's called "usb-bot". It shares most code with "usb-storage", and
> the guest will not be able to see the difference. The qemu command
> -line interface is simliar to usb-uas though, i.e. no automatic scsi
> +line interface is similar to usb-uas though, i.e. no automatic scsi
> disk creation. It also features support for up to 16 LUNs. The LUN
> numbers must be continuous, i.e. for three devices you must use 0+1+2.
> The 0+1+5 numbering from the "usb-uas" example isn't going to work
>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
parent reply other threads:[~2016-12-07 15:53 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20161207123959.4565-1-fziglio@redhat.com>]
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=61c44ab2-01c7-4187-7a5a-6c498f70e31c@redhat.com \
--to=eblake@redhat.com \
--cc=fziglio@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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).