From: Jiri Kosina <jikos@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
linux-input@vger.kernel.org, Jonathan Cameron <jic23@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 v2 0/8] Documentation: HID: edit/correct all files
Date: Mon, 4 Jan 2021 11:51:51 +0100 (CET) [thread overview]
Message-ID: <nycvar.YFH.7.76.2101041151400.13752@cbobk.fhfr.pm> (raw)
In-Reply-To: <20201228205327.1063-1-rdunlap@infradead.org>
On Mon, 28 Dec 2020, Randy Dunlap wrote:
> Make editing corrections to all files in Documentation/hid/.
>
> Cc: Jiri Kosina <jikos@kernel.org>
> Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>
> Cc: linux-input@vger.kernel.org
> Cc: Jonathan Cameron <jic23@kernel.org>
> Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> Cc: linux-iio@vger.kernel.org
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-doc@vger.kernel.org
>
> [PATCH v2 1/8] Documentation: HID: hid-alps editing & corrections
> [PATCH v2 2/8] Documentation: HID: amd-sfh-hid editing & corrections
> [PATCH v2 3/8] Documentation: HID: hiddev editing & corrections
> [PATCH v2 4/8] Documentation: HID: intel-ish-hid editing & corrections
> [PATCH v2 5/8] Documentation: HID: hidraw editing & corrections
> [PATCH v2 6/8] Documentation: HID: hid-sensor editing & corrections
> [PATCH v2 7/8] Documentation: HID: hid-transport editing & corrections
> [PATCH v2 8/8] Documentation: HID: uhid editing & corrections
>
> Documentation/hid/amd-sfh-hid.rst | 22 +++----
> Documentation/hid/hid-alps.rst | 4 -
> Documentation/hid/hid-sensor.rst | 18 +++---
> Documentation/hid/hid-transport.rst | 12 ++--
> Documentation/hid/hiddev.rst | 10 +--
> Documentation/hid/hidraw.rst | 5 +
> Documentation/hid/intel-ish-hid.rst | 78 +++++++++++++-------------
> Documentation/hid/uhid.rst | 34 +++++------
> 8 files changed, 93 insertions(+), 90 deletions(-)
Queued in hid.git#for-5.12/doc. Thanks,
--
Jiri Kosina
SUSE Labs
prev parent reply other threads:[~2021-01-04 10:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 20:53 [PATCH v2 0/8] Documentation: HID: edit/correct all files Randy Dunlap
2020-12-28 20:53 ` [PATCH v2 1/8] Documentation: HID: hid-alps editing & corrections Randy Dunlap
2020-12-28 20:53 ` [PATCH v2 2/8] Documentation: HID: amd-sfh-hid " Randy Dunlap
2020-12-28 20:53 ` [PATCH v2 3/8] Documentation: HID: hiddev " Randy Dunlap
2020-12-28 20:53 ` [PATCH v2 4/8] Documentation: HID: intel-ish-hid " Randy Dunlap
2020-12-28 20:53 ` [PATCH v2 5/8] Documentation: HID: hidraw " Randy Dunlap
2020-12-28 20:53 ` [PATCH v2 6/8] Documentation: HID: hid-sensor " Randy Dunlap
2020-12-28 20:53 ` [PATCH v2 7/8] Documentation: HID: hid-transport " Randy Dunlap
2020-12-28 20:53 ` [PATCH v2 8/8] Documentation: HID: uhid " Randy Dunlap
2020-12-29 13:54 ` [PATCH v2 0/8] Documentation: HID: edit/correct all files Jonathan Cameron
2021-01-04 10:51 ` Jiri Kosina [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=nycvar.YFH.7.76.2101041151400.13752@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=corbet@lwn.net \
--cc=jic23@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=rdunlap@infradead.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).