DMA Engine development
 help / color / mirror / Atom feed
From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: kendra.j.moore3443@gmail.com, gustavoars@kernel.org
Cc: dmaengine@vger.kernel.org
Subject: Re: [PATCH] Fix typo in drivers/dma/qcom/bam_dma.c
Date: Thu, 12 Sep 2024 08:46:23 +0200	[thread overview]
Message-ID: <c9535f84-e354-4c93-ad6f-6ca15b3ea5b7@embeddedor.com> (raw)
In-Reply-To: <20240911195618.94973-1-kendra.j.moore3443@gmail.com>



On 11/09/24 13:56, kendra.j.moore3443@gmail.com wrote:
> From: Kendra Moore <kendra.j.moore3443@gmail.com>
> 
> This patch corrects two spelling errors in this file.
> 
> Signed-off-by: Kendra Moore <kendra.j.moore3443@gmail.com>

Not sure why this was sent to me and not to the maintainers of this
code, but it looks correct, so here you go:

Reviewed-by: Gustavo A. R. Silva <gustavoars@kernel.org>

To get the list of people and mailing lists your patches should be
sent to, run the following command on your patches:

scripts/get_maintainer.pl --nokeywords --nogit --nogit-fallback <path-to-your-patch>

In this case, I ran:

$ scripts/get_maintainer.pl --nokeywords --nogit --nogit-fallback -f drivers/dma/qcom/bam_dma.c
Vinod Koul <vkoul@kernel.org> (maintainer:DMA GENERIC OFFLOAD ENGINE SUBSYSTEM)
linux-arm-msm@vger.kernel.org (open list:ARM/QUALCOMM MAILING LIST)
dmaengine@vger.kernel.org (open list:DMA GENERIC OFFLOAD ENGINE SUBSYSTEM)
linux-kernel@vger.kernel.org (open list)

These are all the people and lists you have to send this changes to.

You can also create an alias to avoid typing the script name and
options every time.

I hope this helps.
--
Gustavo

> ---
>   drivers/dma/qcom/bam_dma.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/dma/qcom/bam_dma.c b/drivers/dma/qcom/bam_dma.c
> index 5e7d332731e0..2d7550b8e03e 100644
> --- a/drivers/dma/qcom/bam_dma.c
> +++ b/drivers/dma/qcom/bam_dma.c
> @@ -440,7 +440,7 @@ static void bam_reset(struct bam_device *bdev)
>   	val |= BAM_EN;
>   	writel_relaxed(val, bam_addr(bdev, 0, BAM_CTRL));
>   
> -	/* set descriptor threshhold, start with 4 bytes */
> +	/* set descriptor threshold, start with 4 bytes */
>   	writel_relaxed(DEFAULT_CNT_THRSHLD,
>   			bam_addr(bdev, 0, BAM_DESC_CNT_TRSHLD));
>   
> @@ -667,7 +667,7 @@ static struct dma_async_tx_descriptor *bam_prep_slave_sg(struct dma_chan *chan,
>   	for_each_sg(sgl, sg, sg_len, i)
>   		num_alloc += DIV_ROUND_UP(sg_dma_len(sg), BAM_FIFO_SIZE);
>   
> -	/* allocate enough room to accomodate the number of entries */
> +	/* allocate enough room to accommodate the number of entries */
>   	async_desc = kzalloc(struct_size(async_desc, desc, num_alloc),
>   			     GFP_NOWAIT);
>   

      reply	other threads:[~2024-09-12  6:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-11 19:56 [PATCH] Fix typo in drivers/dma/qcom/bam_dma.c kendra.j.moore3443
2024-09-12  6:46 ` Gustavo A. R. Silva [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=c9535f84-e354-4c93-ad6f-6ca15b3ea5b7@embeddedor.com \
    --to=gustavo@embeddedor.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=gustavoars@kernel.org \
    --cc=kendra.j.moore3443@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