From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Tom Rix <trix@redhat.com>, <balbi@kernel.org>,
<gregkh@linuxfoundation.org>, <thierry.reding@gmail.com>,
<jonathanh@nvidia.com>, <waynec@nvidia.com>,
<rikard.falkeborn@gmail.com>, <zhangqilong3@huawei.com>,
<jakobkoschel@gmail.com>
Cc: <linux-usb@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usb: gadget: tegra-xudc: clean up comments
Date: Sun, 17 Apr 2022 20:45:24 +0300 [thread overview]
Message-ID: <00d48c81-f289-16db-2e67-8f67468232cb@omp.ru> (raw)
In-Reply-To: <20220416223921.2881719-1-trix@redhat.com>
Hello!
On 4/17/22 1:39 AM, Tom Rix wrote:
> Spelling replacements
> cancelled to canceled
This one was actually correct! :-)
> endpiont to endpoint
> Compliance to Compliance
You meant "Compliacne to Compliance"?
>
> Signed-off-by: Tom Rix <trix@redhat.com>
> ---
> drivers/usb/gadget/udc/tegra-xudc.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/usb/gadget/udc/tegra-xudc.c b/drivers/usb/gadget/udc/tegra-xudc.c
> index d9c406bdb680..0aaf01e1551f 100644
> --- a/drivers/usb/gadget/udc/tegra-xudc.c
> +++ b/drivers/usb/gadget/udc/tegra-xudc.c
[...]
> @@ -3423,7 +3423,7 @@ static void tegra_xudc_device_params_init(struct tegra_xudc *xudc)
> }
>
> /*
> - * Compliacne suite appears to be violating polling LFPS tBurst max
> + * Compliance suite appears to be violating polling LFPS tBurst max
> * of 1.4us. Send 1.45us instead.
> */
> val = xudc_readl(xudc, SSPX_CORE_CNT32);
>
MBR, Sergey
prev parent reply other threads:[~2022-04-17 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 22:39 [PATCH] usb: gadget: tegra-xudc: clean up comments Tom Rix
2022-04-17 0:36 ` Joe Perches
2022-04-17 12:57 ` Tom Rix
2022-04-17 17:45 ` Sergey Shtylyov [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=00d48c81-f289-16db-2e67-8f67468232cb@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jakobkoschel@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rikard.falkeborn@gmail.com \
--cc=thierry.reding@gmail.com \
--cc=trix@redhat.com \
--cc=waynec@nvidia.com \
--cc=zhangqilong3@huawei.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