From: Jonathan Corbet <corbet@lwn.net>
To: Luis de Bethencourt <luisbg@osg.samsung.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
stern@rowland.harvard.edu, oneukum@suse.com,
emilio.lopez@collabora.co.uk, linux-doc@vger.kernel.org
Subject: Re: [PATCH] USB: fix typo in documentation
Date: Mon, 7 Nov 2016 19:12:02 -0700 [thread overview]
Message-ID: <20161107191202.24182679@lwn.net> (raw)
In-Reply-To: <eecda72c-33c3-9945-54dc-d51deb515e9a@osg.samsung.com>
On Tue, 1 Nov 2016 15:23:37 +0000
Luis de Bethencourt <luisbg@osg.samsung.com> wrote:
> A typo sneaked in the latest change on the USB documentation. Fixing it
> and also a trailing whitespace since it is also in the "USB Host-Side API
> Model" chapter.
Applied to the docs tree (with --ignore-whitespace), thanks.
jon
prev parent reply other threads:[~2016-11-08 2:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 15:23 [PATCH] USB: fix typo in documentation Luis de Bethencourt
2016-11-08 2:12 ` Jonathan Corbet [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=20161107191202.24182679@lwn.net \
--to=corbet@lwn.net \
--cc=emilio.lopez@collabora.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luisbg@osg.samsung.com \
--cc=oneukum@suse.com \
--cc=stern@rowland.harvard.edu \
/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).