linux-fpga.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Basheer Ahmed Muddebihal  <basheer.ahmed.muddebihal@linux.intel.com>
To: hao.wu@intel.com, trix@redhat.com, mdf@kernel.org,
	yilun.xu@intel.com, linux-fpga@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: matthew.gerlach@linux.intel.com, marpagan@redhat.com,
	tianfei.zhang@intel.com,
	Basheer Ahmed Muddebihal 
	<basheer.ahmed.muddebihal@linux.intel.com>
Subject: [PATCH 3/3] fpga: dfl: Fix kernel-doc warnings in drivers/fpga/dfl.c
Date: Thu, 19 May 2022 15:12:49 -0700	[thread overview]
Message-ID: <20220519221249.858873-4-basheer.ahmed.muddebihal@linux.intel.com> (raw)
In-Reply-To: <20220519221249.858873-1-basheer.ahmed.muddebihal@linux.intel.com>

Fixed the following warnings:
drivers/fpga/dfl.c:54: warning: cannot understand function prototype: 'struct dfl_dev_info '
drivers/fpga/dfl.c:74: warning: cannot understand function prototype: 'struct dfl_chardev_info '
drivers/fpga/dfl.c:725: warning: Function parameter or member 'revision' not described in 'dfl_feature_info'

Signed-off-by: Basheer Ahmed Muddebihal <basheer.ahmed.muddebihal@linux.intel.com>
---
 drivers/fpga/dfl.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/drivers/fpga/dfl.c b/drivers/fpga/dfl.c
index 6bff39ff21a0..4086cabd25b0 100644
--- a/drivers/fpga/dfl.c
+++ b/drivers/fpga/dfl.c
@@ -45,7 +45,7 @@ static const char *dfl_pdata_key_strings[DFL_ID_MAX] = {
 };
 
 /**
- * dfl_dev_info - dfl feature device information.
+ * struct dfl_dev_info - dfl feature device information.
  * @name: name string of the feature platform device.
  * @dfh_id: id value in Device Feature Header (DFH) register by DFL spec.
  * @id: idr id of the feature dev.
@@ -67,7 +67,7 @@ static struct dfl_dev_info dfl_devs[] = {
 };
 
 /**
- * dfl_chardev_info - chardev information of dfl feature device
+ * struct dfl_chardev_info - chardev information of dfl feature device
  * @name: nmae string of the char device.
  * @devt: devt of the char device.
  */
@@ -708,6 +708,7 @@ struct build_feature_devs_info {
  * struct dfl_feature_info - sub feature info collected during feature dev build
  *
  * @fid: id of this sub feature.
+ * @revision: revision of this sub feature.
  * @mmio_res: mmio resource of this sub feature.
  * @ioaddr: mapped base address of mmio resource.
  * @node: node in sub_features linked list.
-- 
2.34.1


      parent reply	other threads:[~2022-05-19 22:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-19 22:12 [PATCH 0/3] Fix kernel-doc warnings dfl files Basheer Ahmed Muddebihal
2022-05-19 22:12 ` [PATCH 1/3] fpga: dfl: Fix kernel-doc warning in dfl.h for revision Basheer Ahmed Muddebihal
2022-05-28 10:45   ` Xu Yilun
2022-05-19 22:12 ` [PATCH 2/3] fpga: dfl: Fix kernel-doc warnings in include/linux/dfl.h Basheer Ahmed Muddebihal
2022-05-28 10:49   ` Xu Yilun
2022-05-19 22:12 ` Basheer Ahmed Muddebihal [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=20220519221249.858873-4-basheer.ahmed.muddebihal@linux.intel.com \
    --to=basheer.ahmed.muddebihal@linux.intel.com \
    --cc=hao.wu@intel.com \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marpagan@redhat.com \
    --cc=matthew.gerlach@linux.intel.com \
    --cc=mdf@kernel.org \
    --cc=tianfei.zhang@intel.com \
    --cc=trix@redhat.com \
    --cc=yilun.xu@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;
as well as URLs for NNTP newsgroup(s).