From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] scsi: Fix the kerneldoc for scsi_initialize_rq()
Date: Fri, 25 Aug 2017 17:39:40 -0400 [thread overview]
Message-ID: <yq1o9r35ntv.fsf@oracle.com> (raw)
In-Reply-To: <20170824161109.6e23432b@lwn.net> (Jonathan Corbet's message of "Thu, 24 Aug 2017 16:11:09 -0600")
Jonathan,
> The kerneldoc comment for scsi_initialize_rq() neglected to document
> the "rq" parameter, leading to this docs build warning:
Applied to 4.14/scsi-queue. Tweaked the wording based on Bart's
comments. Thank you!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2017-08-25 21:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 22:11 [PATCH] scsi: Fix the kerneldoc for scsi_initialize_rq() Jonathan Corbet
2017-08-24 23:26 ` Bart Van Assche
2017-08-25 21:39 ` Martin K. Petersen [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=yq1o9r35ntv.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=corbet@lwn.net \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox