[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230804214157.iaylzqcmpflx6x7j@intel.intel>
Date: Fri, 4 Aug 2023 23:41:57 +0200
From: Andi Shyti <andi.shyti@...nel.org>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Jarkko Nikula <jarkko.nikula@...ux.intel.com>,
Mario Limonciello <mario.limonciello@....com>,
Wolfram Sang <wsa@...nel.org>, linux-i2c@...r.kernel.org,
linux-kernel@...r.kernel.org,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Jan Dabros <jsd@...ihalf.com>
Subject: Re: [PATCH v1 9/9] i2c: designware: Fix spelling and other issues in
the comments
Hi Andy,
[...]
> @@ -210,12 +210,12 @@ static void psp_release_i2c_bus(void)
> {
> mutex_lock(&psp_i2c_access_mutex);
>
> - /* Return early if mailbox was malfunctional */
> + /* Return early if mailbox was malfunctioned */
I think "was malfunctioned" is not really correct... maybe "has
malfunctioned"? "is malfunctioning"?
> if (psp_i2c_mbox_fail)
> goto cleanup;
[...]
> @@ -508,7 +510,7 @@ void __i2c_dw_disable(struct dw_i2c_dev *dev)
>
> /*
> * Wait 10 times the signaling period of the highest I2C
> - * transfer supported by the driver (for 400KHz this is
> + * transfer supported by the driver (for 400kHz this is
what did you change here? :)
The rest looks good.
Thanks,
Andi
> * 25us) as described in the DesignWare I2C databook.
> */
> usleep_range(25, 250);
Powered by blists - more mailing lists