linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Du Dengke <pinganddu90@gmail.com>
To: jejb@linux.ibm.com, martin.petersen@oracle.com,
	linux-scsi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: __scsi_remove_device: fix comments minor error
Date: Tue, 23 Mar 2021 15:24:08 +0800	[thread overview]
Message-ID: <CAKHP1duT_jQ6pA7WnHPiYvoQvu1vVmAgUDp1kjhnngRufgijgA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 158 bytes --]

Hi experts:
    When I read scsi kernel code, I found a spell error in
__scsi_remove_device function comments. Patch was made in attach file.
Thanks
//dengke

[-- Attachment #2: 0001-__scsi_remove_device-fix-comments-minor-error.patch --]
[-- Type: text/x-patch, Size: 914 bytes --]

From 420e051b624c81d298564c416b5a96188dd0bb6a Mon Sep 17 00:00:00 2001
From: dudengke <dengke.du@ucas.com.cn>
Date: Tue, 23 Mar 2021 10:57:07 +0800
Subject: [PATCH] __scsi_remove_device: fix comments minor error

Signed-off-by: dudengke <dengke.du@ucas.com.cn>
---
 drivers/scsi/scsi_sysfs.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/scsi/scsi_sysfs.c b/drivers/scsi/scsi_sysfs.c
index b6378c8ca783..86e8d0bf821d 100644
--- a/drivers/scsi/scsi_sysfs.c
+++ b/drivers/scsi/scsi_sysfs.c
@@ -1458,7 +1458,7 @@ void __scsi_remove_device(struct scsi_device *sdev)
 
 	/*
 	 * Paired with the kref_get() in scsi_sysfs_initialize().  We have
-	 * remoed sysfs visibility from the device, so make the target
+	 * removed sysfs visibility from the device, so make the target
 	 * invisible if this was the last device underneath it.
 	 */
 	scsi_target_reap(scsi_target(sdev));
-- 
2.25.1


             reply	other threads:[~2021-03-23  7:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23  7:24 Du Dengke [this message]
2021-03-23 16:29 ` __scsi_remove_device: fix comments minor error Bart Van Assche

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=CAKHP1duT_jQ6pA7WnHPiYvoQvu1vVmAgUDp1kjhnngRufgijgA@mail.gmail.com \
    --to=pinganddu90@gmail.com \
    --cc=jejb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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).