From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
linux-scsi@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Yaniv Gardi <ygardi@codeaurora.org>,
Subhash Jadavani <subhashj@codeaurora.org>,
Stanley Chu <stanley.chu@mediatek.com>,
Avri Altman <avri.altman@wdc.com>,
Tomas Winkler <tomas.winkler@intel.com>
Subject: Re: [PATCH 1/3] ufs: Fix kernel-doc warnings
Date: Thu, 31 Oct 2019 22:15:38 -0400 [thread overview]
Message-ID: <yq1eeys5ol1.fsf@oracle.com> (raw)
In-Reply-To: <20191029230710.211926-2-bvanassche@acm.org> (Bart Van Assche's message of "Tue, 29 Oct 2019 16:07:08 -0700")
Bart,
> Fix the following three kernel-doc warnings:
>
> drivers/scsi/ufs/ufs_bsg.c:165: warning: Function parameter or member 'hba' not described in 'ufs_bsg_remove'
> drivers/scsi/ufs/ufshcd.c:5789: warning: Function parameter or member 'cmd_type' not described in 'ufshcd_issue_devman_upiu_cmd'
> drivers/scsi/ufs/ufshcd.c:5789: warning: Excess function parameter 'msgcode' description in 'ufshcd_issue_devman_upiu_cmd'
Applied to 5.5/scsi-queue, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2019-11-01 2:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 23:07 [PATCH 0/3] Three small UFS patches Bart Van Assche
2019-10-29 23:07 ` [PATCH 1/3] ufs: Fix kernel-doc warnings Bart Van Assche
2019-10-30 11:20 ` Avri Altman
2019-11-01 2:15 ` Martin K. Petersen [this message]
2019-10-29 23:07 ` [PATCH 2/3] ufs: Use enum dev_cmd_type where appropriate Bart Van Assche
2019-10-30 11:25 ` Avri Altman
2019-11-01 2:16 ` Martin K. Petersen
2019-10-29 23:07 ` [PATCH 3/3] ufs: Remove .setup_xfer_req() Bart Van Assche
2019-10-30 11:19 ` Avri Altman
2019-11-04 12:57 ` Avri Altman
2019-11-05 16:17 ` Alim Akhtar
2019-11-06 4:09 ` Alim Akhtar
2019-11-06 4:45 ` Bart Van Assche
2019-11-06 5:04 ` Martin K. Petersen
2019-11-05 5:01 ` Martin K. Petersen
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=yq1eeys5ol1.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=stanley.chu@mediatek.com \
--cc=subhashj@codeaurora.org \
--cc=tomas.winkler@intel.com \
--cc=ygardi@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.