mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans Zhang <18255117159@163.com>
To: ldewangan@nvidia.com, andi.shyti@kernel.org,
	thierry.reding@gmail.com, jonathanh@nvidia.com
Cc: digetx@gmail.com, linux-i2c@vger.kernel.org,
	linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
	hans.zhang@cixtech.com
Subject: Re: [PATCH] i2c: tegra: Add missing kernel-doc for dma_dev member
Date: Fri, 13 Jun 2025 00:37:57 +0800	[thread overview]
Message-ID: <e218509e-50f4-4c30-b52a-a53263ebe394@163.com> (raw)
In-Reply-To: <20250522163814.399630-1-18255117159@163.com>

Hi all,

Gentle ping.

Best regards,
Hans

On 2025/5/23 00:38, Hans Zhang wrote:
> Fix the kernel-doc warning by describing the 'dma_dev' member in
> the tegra_i2c_dev struct.  This resolves the compilation warning:
> 
> drivers/i2c/busses/i2c-tegra.c:297: warning: Function parameter or struct member 'dma_dev' not described in 'tegra_i2c_dev'
> 
> Fixes: cdbf26251d3b ("i2c: tegra: Allocate DMA memory for DMA engine")
> Signed-off-by: Hans Zhang <18255117159@163.com>
> ---
>   drivers/i2c/busses/i2c-tegra.c | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/i2c/busses/i2c-tegra.c b/drivers/i2c/busses/i2c-tegra.c
> index 87976e99e6d0..07bb1e7e84cc 100644
> --- a/drivers/i2c/busses/i2c-tegra.c
> +++ b/drivers/i2c/busses/i2c-tegra.c
> @@ -253,6 +253,7 @@ struct tegra_i2c_hw_feature {
>    * @dma_phys: handle to DMA resources
>    * @dma_buf: pointer to allocated DMA buffer
>    * @dma_buf_size: DMA buffer size
> + * @dma_dev: DMA device used for transfers
>    * @dma_mode: indicates active DMA transfer
>    * @dma_complete: DMA completion notifier
>    * @atomic_mode: indicates active atomic transfer
> 
> base-commit: fee3e843b309444f48157e2188efa6818bae85cf


  reply	other threads:[~2025-06-12 16:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-22 16:38 Hans Zhang
2025-06-12 16:37 ` Hans Zhang [this message]
2025-06-25 21:02 ` Andi Shyti
  -- strict thread matches above, loose matches on Subject: below --
2025-05-22 16:32 Hans Zhang
2025-05-22 16:35 ` Krzysztof Wilczyński
2025-05-22 16:39   ` Hans Zhang
2025-05-22 16:40     ` Hans Zhang
2025-05-22 16:42     ` Krzysztof Wilczyński
2025-05-22 16:37 ` Hans Zhang

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=e218509e-50f4-4c30-b52a-a53263ebe394@163.com \
    --to=18255117159@163.com \
    --cc=andi.shyti@kernel.org \
    --cc=digetx@gmail.com \
    --cc=hans.zhang@cixtech.com \
    --cc=jonathanh@nvidia.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=thierry.reding@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

all inboxes | Powered by JetHome®