From: Heiko Carstens <hca@linux.ibm.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
linux-s390@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 23/35] Documentation: s390: correct spelling
Date: Fri, 27 Jan 2023 12:43:19 +0100 [thread overview]
Message-ID: <Y9O4150V0hMBsEoj@osiris> (raw)
In-Reply-To: <20230127064005.1558-24-rdunlap@infradead.org>
On Thu, Jan 26, 2023 at 10:39:53PM -0800, Randy Dunlap wrote:
> Correct spelling problems for Documentation/s390/ as reported
> by codespell.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Heiko Carstens <hca@linux.ibm.com>
> Cc: Vasily Gorbik <gor@linux.ibm.com>
> Cc: Alexander Gordeev <agordeev@linux.ibm.com>
> Cc: linux-s390@vger.kernel.org
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-doc@vger.kernel.org
> ---
> Documentation/s390/pci.rst | 4 ++--
> Documentation/s390/vfio-ccw.rst | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
FWIW,
Acked-by: Heiko Carstens <hca@linux.ibm.com>
If you expect me to pick this up via the s390 tree, please let me know.
next prev parent reply other threads:[~2023-01-27 12:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 6:39 [PATCH 00/35] Documentation: correct lots of spelling errors (series 1) Randy Dunlap
2023-01-27 6:39 ` [PATCH 23/35] Documentation: s390: correct spelling Randy Dunlap
2023-01-27 11:43 ` Heiko Carstens [this message]
2023-01-28 10:48 ` (subset) [PATCH 00/35] Documentation: correct lots of spelling errors (series 1) Mark Brown
2023-01-28 20:30 ` patchwork-bot+netdevbpf
2023-01-31 16:28 ` (subset) " Catalin Marinas
2023-02-14 16:57 ` 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=Y9O4150V0hMBsEoj@osiris \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=corbet@lwn.net \
--cc=gor@linux.ibm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=rdunlap@infradead.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