From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Colin King <colin.king@canonical.com>,
Vinod Koul <vkoul@kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
Grygorii Strashko <grygorii.strashko@ti.com>,
<dmaengine@vger.kernel.org>
Cc: <kernel-janitors@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][next] dmaengine: ti: k3-udma: fix spelling mistake "limted" -> "limited"
Date: Wed, 22 Jan 2020 13:09:50 +0200 [thread overview]
Message-ID: <e642e0c4-b712-a3de-1444-0c7de6243284@ti.com> (raw)
In-Reply-To: <20200122093818.2800743-1-colin.king@canonical.com>
Colin,
On 22/01/2020 11.38, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There are spelling mistakes in dev_err messages. Fix them.
This slipped through, thanks for catching it!
Acked-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/dma/ti/k3-udma.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/dma/ti/k3-udma.c b/drivers/dma/ti/k3-udma.c
> index 9974e72cdc50..ea79c2df28e0 100644
> --- a/drivers/dma/ti/k3-udma.c
> +++ b/drivers/dma/ti/k3-udma.c
> @@ -2300,7 +2300,7 @@ udma_prep_slave_sg(struct dma_chan *chan, struct scatterlist *sgl,
> /* static TR for remote PDMA */
> if (udma_configure_statictr(uc, d, dev_width, burst)) {
> dev_err(uc->ud->dev,
> - "%s: StaticTR Z is limted to maximum 4095 (%u)\n",
> + "%s: StaticTR Z is limited to maximum 4095 (%u)\n",
> __func__, d->static_tr.bstcnt);
>
> udma_free_hwdesc(uc, d);
> @@ -2483,7 +2483,7 @@ udma_prep_dma_cyclic(struct dma_chan *chan, dma_addr_t buf_addr, size_t buf_len,
> /* static TR for remote PDMA */
> if (udma_configure_statictr(uc, d, dev_width, burst)) {
> dev_err(uc->ud->dev,
> - "%s: StaticTR Z is limted to maximum 4095 (%u)\n",
> + "%s: StaticTR Z is limited to maximum 4095 (%u)\n",
> __func__, d->static_tr.bstcnt);
>
> udma_free_hwdesc(uc, d);
>
- Péter
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
next prev parent reply other threads:[~2020-01-22 11:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 9:38 Colin King
2020-01-22 11:09 ` Peter Ujfalusi [this message]
2020-01-23 11:33 ` Vinod Koul
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=e642e0c4-b712-a3de-1444-0c7de6243284@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=colin.king@canonical.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vkoul@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®