From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 03/35] Documentation: block: correct spelling
Date: Fri, 27 Jan 2023 15:31:54 +0700 [thread overview]
Message-ID: <Y9OL+iyaQtXLSCKc@debian.me> (raw)
In-Reply-To: <20230127064005.1558-4-rdunlap@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 790 bytes --]
On Thu, Jan 26, 2023 at 10:39:33PM -0800, Randy Dunlap wrote:
> diff -- a/Documentation/block/data-integrity.rst b/Documentation/block/data-integrity.rst
> --- a/Documentation/block/data-integrity.rst
> +++ b/Documentation/block/data-integrity.rst
> @@ -209,7 +209,7 @@ will require extra work due to the appli
> sector must be set, and the bio should have all data pages
> added. It is up to the caller to ensure that the bio does not
> change while I/O is in progress.
> - Complete bio with error if prepare failed for some reson.
> + Complete bio with error if prepare failed for some reason.
>
So if prepare returns error, bio is completed not successfully but also
errored?
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-01-27 8:32 UTC|newest]
Thread overview: 9+ 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 03/35] Documentation: block: correct spelling Randy Dunlap
2023-01-27 8:31 ` Bagas Sanjaya [this message]
2023-01-27 22:58 ` Randy Dunlap
2023-01-27 8:36 ` Mukesh Ojha
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=Y9OL+iyaQtXLSCKc@debian.me \
--to=bagasdotme@gmail.com \
--cc=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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