public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Xu Yilun <yilun.xu@linux.intel.com>,
	Peter Colberg <peter.colberg@intel.com>
Cc: Wu Hao <hao.wu@intel.com>, Tom Rix <trix@redhat.com>,
	Moritz Fischer <mdf@kernel.org>, Xu Yilun <yilun.xu@intel.com>,
	Alan Tull <atull@kernel.org>, Shiva Rao <shiva.rao@intel.com>,
	Kang Luwei <luwei.kang@intel.com>,
	Enno Luebbers <enno.luebbers@intel.com>,
	linux-fpga@vger.kernel.org, linux-kernel@vger.kernel.org,
	Russ Weight <russ.weight@linux.dev>,
	Marco Pagani <marpagan@redhat.com>,
	Matthew Gerlach <matthew.gerlach@linux.intel.com>,
	kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] fpga: dfl: fme: fix kernel-doc comments for some functions
Date: Mon, 1 Apr 2024 21:42:54 -0700	[thread overview]
Message-ID: <fb49e921-a765-4828-bcfe-b2b4e623c5ea@infradead.org> (raw)
In-Reply-To: <Zgt/wftzm4xthfio@yilunxu-OptiPlex-7050>



On 4/1/24 8:47 PM, Xu Yilun wrote:
> On Thu, Mar 28, 2024 at 08:15:42PM -0400, Peter Colberg wrote:
>> From: Xu Yilun <yilun.xu@intel.com>
> 
> I didn't remember I wrote this exact patch, but anyway the patch itself
> is confusing.
> 
>>
>> lkp reported 2 build warnings:
>>
>>    drivers/fpga/dfl/dfl-fme-pr.c:175: warning: Function parameter or member 'feature' not described in 'dfl_fme_create_mgr'
>>
>>>> drivers/fpga/dfl/dfl-fme-pr.c:280: warning: expecting prototype for
>>>> dfl_fme_destroy_bridge(). Prototype was for dfl_fme_destroy_bridges()
>>>> instead
>>
>> Fixes: 29de76240e86 ("fpga: dfl: fme: add partial reconfiguration sub feature support")
>> Reported-by: kernel test robot <lkp@intel.com>
>> Signed-off-by: Xu Yilun <yilun.xu@intel.com>
>> Signed-off-by: Peter Colberg <peter.colberg@intel.com>

All kernel-doc issues with this source file are already fixed in linux-next
by this commit:

commit 782d8e61b5d6
Author: Randy Dunlap <rdunlap@infradead.org>
Date:   Thu Jan 12 22:37:20 2023 -0800

    fpga: dfl: kernel-doc corrections
    
    Fix W=1 kernel-doc warnings in drivers/fpga/:


>> ---
>>  drivers/fpga/dfl-fme-pr.c | 3 ++-
>>  1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/fpga/dfl-fme-pr.c b/drivers/fpga/dfl-fme-pr.c
>> index cdcf6dea4cc9..96cb24787ab1 100644
>> --- a/drivers/fpga/dfl-fme-pr.c
>> +++ b/drivers/fpga/dfl-fme-pr.c
>> @@ -166,6 +166,7 @@ static int fme_pr(struct platform_device *pdev, unsigned long arg)
>>   * dfl_fme_create_mgr - create fpga mgr platform device as child device
>>   * @feature: sub feature info
> 
> The member 'feature' is described here. It still causes build warning?
> 
>>   * @pdata: fme platform_device's pdata
>> + * @feature: the dfl fme PR sub feature
> 
> Why adding a duplicated item would fix the warning?
> 
>>   *
>>   * Return: mgr platform device if successful, and error code otherwise.
>>   */
>> @@ -273,7 +274,7 @@ static void dfl_fme_destroy_bridge(struct dfl_fme_bridge *fme_br)
>>  }
>>  
>>  /**
>> - * dfl_fme_destroy_bridges - destroy all fpga bridge platform device
> 
> The prototype is for dfl_fme_destroy_bridges(), why the warning?
> 
>> + * dfl_fme_destroy_bridges - destroy all fpga bridge platform devices
> 
> Correct the plural form in description would fix the warning?
> 
>>   * @pdata: fme platform device's pdata
>>   */
>>  static void dfl_fme_destroy_bridges(struct dfl_feature_platform_data *pdata)
>> -- 
>> 2.44.0
>>
>>
> 

-- 
#Randy

  reply	other threads:[~2024-04-02  4:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-29  0:15 [PATCH] fpga: dfl: fme: fix kernel-doc comments for some functions Peter Colberg
2024-04-02  3:47 ` Xu Yilun
2024-04-02  4:42   ` Randy Dunlap [this message]
2024-04-02 20:17     ` Colberg, Peter

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=fb49e921-a765-4828-bcfe-b2b4e623c5ea@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=atull@kernel.org \
    --cc=enno.luebbers@intel.com \
    --cc=hao.wu@intel.com \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=luwei.kang@intel.com \
    --cc=marpagan@redhat.com \
    --cc=matthew.gerlach@linux.intel.com \
    --cc=mdf@kernel.org \
    --cc=peter.colberg@intel.com \
    --cc=russ.weight@linux.dev \
    --cc=shiva.rao@intel.com \
    --cc=trix@redhat.com \
    --cc=yilun.xu@intel.com \
    --cc=yilun.xu@linux.intel.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