From: Randy Dunlap <rdunlap@infradead.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-kernel@vger.kernel.org, Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
linux-input@vger.kernel.org,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
linux-iio@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 2/8] Documentation: HID: amd-sfh-hid editing & corrections
Date: Sun, 13 Dec 2020 16:55:44 -0800 [thread overview]
Message-ID: <0264d355-818f-ea2f-97a1-85663d5ce81c@infradead.org> (raw)
In-Reply-To: <20201205171247.5225d844@archlinux>
On 12/5/20 9:12 AM, Jonathan Cameron wrote:
> On Thu, 3 Dec 2020 22:20:16 -0800
> Randy Dunlap <rdunlap@infradead.org> wrote:
>
>> Do basic editing & correction to amd-sfh-hid.rst:
>> - fix punctuation
>> - use HID instead of hid consistently
>> - fix grammar, verb tense
Hi Jonathan,
Thanks for all the comments.
I'll send a v2.
--
~Randy
next prev parent reply other threads:[~2020-12-14 0:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 6:20 [PATCH 0/8] Documentation: HID: edit/correct all files Randy Dunlap
2020-12-04 6:20 ` [PATCH 1/8] Documentation: HID: hid-alps editing & corrections Randy Dunlap
2020-12-04 6:20 ` [PATCH 2/8] Documentation: HID: amd-sfh-hid " Randy Dunlap
2020-12-05 17:12 ` Jonathan Cameron
2020-12-14 0:55 ` Randy Dunlap [this message]
2020-12-04 6:20 ` [PATCH 3/8] Documentation: HID: hiddev " Randy Dunlap
2020-12-05 17:17 ` Jonathan Cameron
2020-12-04 6:20 ` [PATCH 4/8] Documentation: HID: intel-ish-hid " Randy Dunlap
2020-12-05 17:24 ` Jonathan Cameron
2020-12-04 6:20 ` [PATCH 5/8] Documentation: HID: hidraw " Randy Dunlap
2020-12-04 6:20 ` [PATCH 6/8] Documentation: HID: hid-sensor " Randy Dunlap
2020-12-04 6:20 ` [PATCH 7/8] Documentation: HID: hid-transport " Randy Dunlap
2020-12-04 6:20 ` [PATCH 8/8] Documentation: HID: uhid " Randy Dunlap
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=0264d355-818f-ea2f-97a1-85663d5ce81c@infradead.org \
--to=rdunlap@infradead.org \
--cc=benjamin.tissoires@redhat.com \
--cc=corbet@lwn.net \
--cc=jic23@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.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;
as well as URLs for NNTP newsgroup(s).