From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
nvdimm@lists.linux.dev, Vinod Koul <vkoul@kernel.org>,
dmaengine@vger.kernel.org, Song Liu <song@kernel.org>,
linux-raid@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH 2/9] Documentation: driver-api: correct spelling
Date: Tue, 31 Jan 2023 10:10:40 +0100 [thread overview]
Message-ID: <Y9jbEDPHbBb1hbsZ@kroah.com> (raw)
In-Reply-To: <20230129231053.20863-3-rdunlap@infradead.org>
On Sun, Jan 29, 2023 at 03:10:46PM -0800, Randy Dunlap wrote:
> Correct spelling problems for Documentation/driver-api/ as reported
> by codespell.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-doc@vger.kernel.org
> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
> Cc: linux-media@vger.kernel.org
> Cc: Dan Williams <dan.j.williams@intel.com>
> Cc: Vishal Verma <vishal.l.verma@intel.com>
> Cc: Dave Jiang <dave.jiang@intel.com>
> Cc: nvdimm@lists.linux.dev
> Cc: Vinod Koul <vkoul@kernel.org>
> Cc: dmaengine@vger.kernel.org
> Cc: Song Liu <song@kernel.org>
> Cc: linux-raid@vger.kernel.org
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: linux-usb@vger.kernel.org
> ---
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2023-01-31 9:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 23:10 [PATCH 0/9] Documentation: correct lots of spelling errors (series 2) Randy Dunlap
2023-01-29 23:10 ` [PATCH 1/9] Documentation: admin-guide: correct spelling Randy Dunlap
2023-01-30 9:35 ` Mukesh Ojha
2023-01-29 23:10 ` [PATCH 2/9] Documentation: driver-api: " Randy Dunlap
2023-01-30 19:11 ` Dan Williams
2023-01-30 19:45 ` Song Liu
2023-01-31 9:10 ` Greg Kroah-Hartman [this message]
2023-01-29 23:10 ` [PATCH 3/9] Documentation: hwmon: " Randy Dunlap
2023-01-30 0:39 ` Guenter Roeck
2023-01-29 23:10 ` [PATCH 4/9] Documentation: networking: " Randy Dunlap
2023-01-29 23:10 ` [PATCH 5/9] Documentation: RCU: " Randy Dunlap
2023-01-30 5:24 ` Paul E. McKenney
2023-01-29 23:10 ` [PATCH 6/9] Documentation: scsi/ChangeLog*: " Randy Dunlap
2023-01-29 23:10 ` [PATCH 7/9] Documentation: scsi: " Randy Dunlap
2023-01-29 23:10 ` [PATCH 8/9] Documentation: sparc: " Randy Dunlap
2023-01-29 23:10 ` [PATCH 9/9] Documentation: userspace-api: " Randy Dunlap
2023-01-31 12:10 ` [PATCH 0/9] Documentation: correct lots of spelling errors (series 2) patchwork-bot+netdevbpf
2023-01-31 12:17 ` Paolo Abeni
2023-02-02 18:09 ` Jonathan Corbet
2023-02-02 18:33 ` Randy Dunlap
2023-02-02 18:39 ` [dm-devel] " Bart Van Assche
2023-02-02 18:46 ` Jonathan Corbet
2023-02-02 18:54 ` James Bottomley
2023-02-08 23:32 ` Martin K. Petersen
2023-02-14 16:57 ` (subset) " Martin K. Petersen
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=Y9jbEDPHbBb1hbsZ@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=rdunlap@infradead.org \
--cc=song@kernel.org \
--cc=vishal.l.verma@intel.com \
--cc=vkoul@kernel.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).