linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiang Jian <jiangjian@cdjrlc.com>
To: axboe@kernel.dk
Cc: philipp.reisner@linbit.com, lars.ellenberg@linbit.com,
	christoph.boehmwalder@linbit.com, drbd-dev@lists.linbit.com,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jiang Jian <jiangjian@cdjrlc.com>
Subject: [PATCH] block: drbd: drbd_state: Fix typo in comments
Date: Wed, 22 Jun 2022 23:52:20 +0800	[thread overview]
Message-ID: <20220622155220.8704-1-jiangjian@cdjrlc.com> (raw)

Replace 'is' with 'it'

file: drivers/block/drbd/drbd_state.c
line: 1900

* But is is still not save to dreference ldev here, since

changed to:

* But it is still not save to dreference ldev here, since

Signed-off-by: Jiang Jian <jiangjian@cdjrlc.com>
---
 drivers/block/drbd/drbd_state.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/block/drbd/drbd_state.c b/drivers/block/drbd/drbd_state.c
index 3f7bf9f2d874..99927c44f0c3 100644
--- a/drivers/block/drbd/drbd_state.c
+++ b/drivers/block/drbd/drbd_state.c
@@ -1897,7 +1897,7 @@ static void after_state_ch(struct drbd_device *device, union drbd_state os,
 		int was_io_error = 0;
 		/* corresponding get_ldev was in _drbd_set_state, to serialize
 		 * our cleanup here with the transition to D_DISKLESS.
-		 * But is is still not save to dreference ldev here, since
+		 * But it is still not save to dreference ldev here, since
 		 * we might come from an failed Attach before ldev was set. */
 		if (device->ldev) {
 			rcu_read_lock();
-- 
2.17.1


             reply	other threads:[~2022-06-22 15:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 15:52 Jiang Jian [this message]
2022-06-22 16:10 ` [PATCH] block: drbd: drbd_state: Fix typo in comments James Bottomley
2022-06-22 20:57 ` Christoph Böhmwalder

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=20220622155220.8704-1-jiangjian@cdjrlc.com \
    --to=jiangjian@cdjrlc.com \
    --cc=axboe@kernel.dk \
    --cc=christoph.boehmwalder@linbit.com \
    --cc=drbd-dev@lists.linbit.com \
    --cc=lars.ellenberg@linbit.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philipp.reisner@linbit.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).