From: Diego Viola <diego.viola@gmail.com>
To: damien.lemoal@opensource.wdc.com
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
corbet@lwn.net, Diego Viola <diego.viola@gmail.com>
Subject: [PATCH] ata: libata-core: fix "it's" typos
Date: Wed, 23 Mar 2022 02:40:01 -0300 [thread overview]
Message-ID: <20220323054001.17344-1-diego.viola@gmail.com> (raw)
Use the contraction "it's" instead of the possessive form "its".
Signed-off-by: Diego Viola <diego.viola@gmail.com>
---
drivers/ata/libata-core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
index 0c854aebfe0b..22c93589f2c4 100644
--- a/drivers/ata/libata-core.c
+++ b/drivers/ata/libata-core.c
@@ -1398,7 +1398,7 @@ unsigned long ata_id_xfermask(const u16 *id)
/* But wait.. there's more. Design your standards by
* committee and you too can get a free iordy field to
- * process. However its the speeds not the modes that
+ * process. However it's the speeds not the modes that
* are supported... Note drivers using the timing API
* will get this right anyway
*/
@@ -5603,7 +5603,7 @@ static void ata_finalize_port_ops(struct ata_port_operations *ops)
* Start and then freeze ports of @host. Started status is
* recorded in host->flags, so this function can be called
* multiple times. Ports are guaranteed to get started only
- * once. If host->ops isn't initialized yet, its set to the
+ * once. If host->ops isn't initialized yet, it's set to the
* first non-dummy port ops.
*
* LOCKING:
--
2.35.1
next reply other threads:[~2022-03-23 5:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 5:40 Diego Viola [this message]
2022-03-23 5:45 ` Damien Le Moal
2022-03-23 5:52 ` Diego Viola
2022-03-23 5:53 ` Damien Le Moal
2022-03-23 7:24 ` Diego Viola
2022-03-23 8:17 ` Damien Le Moal
2022-03-23 8:44 ` Diego Viola
2022-03-24 4:14 ` Damien Le Moal
2022-03-24 6:21 ` Diego Viola
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=20220323054001.17344-1-diego.viola@gmail.com \
--to=diego.viola@gmail.com \
--cc=corbet@lwn.net \
--cc=damien.lemoal@opensource.wdc.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®