From: Pierre Yves MORDRET <pierre-yves.mordret@foss.st.com>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
<coquelin.stm32@gmail.com>,
Alexandre TORGUE <alexandre.torgue@st.com>,
<p.zabel@pengutronix.de>, <linux-i2c@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: <rdunlap@infradead.org>
Subject: Re: [PATCH] i2c-stm32f4: Mundane typo fix
Date: Thu, 25 Mar 2021 10:24:11 +0100 [thread overview]
Message-ID: <39f76c98-2f83-76ee-a1a3-3db0dcdc70ca@foss.st.com> (raw)
In-Reply-To: <AS8PR10MB4504462766AFA3E151121462C6629@AS8PR10MB4504.EURPRD10.PROD.OUTLOOK.COM>
On 3/25/21 10:19 AM, Pierre Yves MORDRET wrote:
>
> s/postion/position/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> ---
> drivers/i2c/busses/i2c-stm32f4.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/i2c/busses/i2c-stm32f4.c b/drivers/i2c/busses/i2c-stm32f4.c
> index 937c2c8fd349..4933fc8ce3fd 100644
> --- a/drivers/i2c/busses/i2c-stm32f4.c
> +++ b/drivers/i2c/busses/i2c-stm32f4.c
> @@ -534,7 +534,7 @@ static void stm32f4_i2c_handle_rx_addr(struct stm32f4_i2c_dev *i2c_dev)
> default:
> /*
> * N-byte reception:
> - * Enable ACK, reset POS (ACK postion) and clear ADDR flag.
> + * Enable ACK, reset POS (ACK position) and clear ADDR flag.
> * In that way, ACK will be sent as soon as the current byte
> * will be received in the shift register
> */
Hi All,
Reviewed-by: Pierre-Yves MORDRET <pierre-yves.mordret@foss.st.com>
> --
> 2.30.1
>
Regards
--
--
~ Py MORDRET
--
next prev parent reply other threads:[~2021-03-25 9:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 14:06 [PATCH] i2c-stm32f4: Mundane typo fix Bhaskar Chowdhury
2021-03-24 21:49 ` Randy Dunlap
2021-03-25 7:43 ` Alain Volmat
[not found] ` <AS8PR10MB4504462766AFA3E151121462C6629@AS8PR10MB4504.EURPRD10.PROD.OUTLOOK.COM>
2021-03-25 9:24 ` Pierre Yves MORDRET [this message]
2021-03-31 7:55 ` Wolfram Sang
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=39f76c98-2f83-76ee-a1a3-3db0dcdc70ca@foss.st.com \
--to=pierre-yves.mordret@foss.st.com \
--cc=alexandre.torgue@st.com \
--cc=coquelin.stm32@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=p.zabel@pengutronix.de \
--cc=rdunlap@infradead.org \
--cc=unixbhaskar@gmail.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).