From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Wang Honghui <honghui.wang@ucas.com.cn>,
Oliver Neukum <oliver@neukum.org>, Ali Akcaagac <aliakc@web.de>,
Jamie Lenehan <lenehan@twibble.org>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
dc395x@twibble.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] strcuture: Correct spelling mistakes in comments
Date: Thu, 4 May 2023 17:07:59 +0700 [thread overview]
Message-ID: <ZFOD/6rT36evHXNz@debian.me> (raw)
In-Reply-To: <262EBDA8BEEA7619+ZFN1b1D66/Lp8hzh@TP-P15V>
[-- Attachment #1: Type: text/plain, Size: 2302 bytes --]
On Thu, May 04, 2023 at 05:05:51PM +0800, Wang Honghui wrote:
> Subject: [PATCH] strcuture: Correct spelling mistakes in comments
The patch subject should have been "scsi: dc395x: Correct 'structures'
spelling mistakes". For the description, though, I'd like to write
as 'As title', since the subject is self-explanatory.
Care to reroll?
>
> Signed-off-by: Wang Honghui <honghui.wang@ucas.com.cn>
> ---
> drivers/scsi/dc395x.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/scsi/dc395x.c b/drivers/scsi/dc395x.c
> index c8e86f8a631e..a3f00e6e3296 100644
> --- a/drivers/scsi/dc395x.c
> +++ b/drivers/scsi/dc395x.c
> @@ -3641,7 +3641,7 @@ static void adapter_add_device(struct AdapterCtlBlk *acb,
> * adapter_remove_device - Removes the device instance from the adaptor
> * instance. The device instance is not check in any way or freed by this.
> * The caller is expected to take care of that. This will simply remove the
> - * device from the adapters data strcutures.
> + * device from the adapters data structures.
> *
> * @acb: The adapter device to be updated
> * @dcb: A device that has previously been added to the adapter.
> @@ -3980,7 +3980,7 @@ static void trms1040_read_all(struct NvRamType *eeprom, unsigned long io_port)
> * Checks the checksum and if it's not correct it uses a set of default
> * values.
> *
> - * @eeprom: caller allocated strcuture to read the eeprom data into
> + * @eeprom: caller allocated structure to read the eeprom data into
> * @io_port: io port to read from
> **/
> static void check_eeprom(struct NvRamType *eeprom, unsigned long io_port)
> @@ -4578,7 +4578,7 @@ static void banner_display(void)
> * dc395x_init_one - Initialise a single instance of the adapter.
> *
> * The PCI layer will call this once for each instance of the adapter
> - * that it finds in the system. The pci_dev strcuture indicates which
> + * that it finds in the system. The pci_dev structure indicates which
> * instance we are being called from.
> *
> * @dev: The PCI device to initialize.
The diff LGTM, thanks!
For the diff only,
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-05-04 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 9:05 [PATCH] strcuture: Correct spelling mistakes in comments Wang Honghui
2023-05-04 10:07 ` Bagas Sanjaya [this message]
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=ZFOD/6rT36evHXNz@debian.me \
--to=bagasdotme@gmail.com \
--cc=aliakc@web.de \
--cc=dc395x@twibble.org \
--cc=honghui.wang@ucas.com.cn \
--cc=jejb@linux.ibm.com \
--cc=lenehan@twibble.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=oliver@neukum.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