lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ac99cc8e-11c2-d96b-9ce1-ce5618b7b378@opensource.wdc.com>
Date:   Wed, 23 Mar 2022 14:45:12 +0900
From:   Damien Le Moal <damien.lemoal@...nsource.wdc.com>
To:     Diego Viola <diego.viola@...il.com>
Cc:     linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org,
        corbet@....net
Subject: Re: [PATCH] ata: libata-core: fix "it's" typos

On 3/23/22 14:40, Diego Viola wrote:
> Use the contraction "it's" instead of the possessive form "its".

Well, while at it, let's use proper formal written English, so:
s/it's/it is
s/isn't/is not

> 
> Signed-off-by: Diego Viola <diego.viola@...il.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:


-- 
Damien Le Moal
Western Digital Research

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ