From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: linux-scsi@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
Doug Gilbert <dgilbert@interlog.com>,
Sagi Grimberg <sagi@grimberg.me>,
Max Gurtovoy <mgurtovoy@nvidia.com>,
linux-rdma@vger.kernel.org, target-devel@vger.kernel.org,
Hannes Reinecke <hare@suse.de>,
Bart Van Assche <bvanassche@acm.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 0/8] scsi: documentation: clean up docs and fix kernel-doc
Date: Thu, 11 Apr 2024 22:05:14 -0400 [thread overview]
Message-ID: <171288602656.3729249.13953839600529757224.b4-ty@oracle.com> (raw)
In-Reply-To: <20240408025425.18778-1-rdunlap@infradead.org>
On Sun, 07 Apr 2024 19:54:17 -0700, Randy Dunlap wrote:
> Clean up some SCSI doc files and fix kernel-doc in 6 header files in
> include/scsi/.
>
>
> [PATCH 1/8] scsi: documentation: clean up overview
> [PATCH 2/8] scsi: documentation: clean up scsi_mid_low_api.rst
> [PATCH 3/8] scsi: core: add kernel-doc for scsi_msg_to_host_byte()
> [PATCH 4/8] scsi: iser: fix @read_stag kernel-doc warning
> [PATCH 5/8] scsi: libfcoe: fix a slew of kernel-doc warnings
> [PATCH 6/8] scsi: core: add function return kernel-doc for 2 functions
> [PATCH 7/8] scsi: scsi_transport_fc: add kernel-doc for function return
> [PATCH 8/8] scsi: scsi_transport_srp: fix a couple of kernel-doc warnings
>
> [...]
Applied to 6.10/scsi-queue, thanks!
[1/8] scsi: documentation: clean up scsi_mid_low_api.rst
https://git.kernel.org/mkp/scsi/c/c3bf7774fa24
[2/8] scsi: documentation: clean up overview
https://git.kernel.org/mkp/scsi/c/293fcea539b5
[3/8] scsi: core: add kernel-doc for scsi_msg_to_host_byte()
https://git.kernel.org/mkp/scsi/c/fcf8829fd993
[4/8] scsi: iser: fix @read_stag kernel-doc warning
https://git.kernel.org/mkp/scsi/c/11d99e91846a
[5/8] scsi: libfcoe: fix a slew of kernel-doc warnings
https://git.kernel.org/mkp/scsi/c/d9c911824145
[6/8] scsi: core: add function return kernel-doc for 2 functions
https://git.kernel.org/mkp/scsi/c/8d523f0f5383
[7/8] scsi: scsi_transport_fc: add kernel-doc for function return
https://git.kernel.org/mkp/scsi/c/007c04e53526
[8/8] scsi: scsi_transport_srp: fix a couple of kernel-doc warnings
https://git.kernel.org/mkp/scsi/c/a2530eb748ff
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2024-04-12 2:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 2:54 [PATCH 0/8] scsi: documentation: clean up docs and fix kernel-doc Randy Dunlap
2024-04-08 2:54 ` [PATCH 4/8] scsi: iser: fix @read_stag kernel-doc warning Randy Dunlap
2024-04-08 6:35 ` Sagi Grimberg
2024-04-08 7:43 ` Max Gurtovoy
2024-04-09 2:10 ` [PATCH 0/8] scsi: documentation: clean up docs and fix kernel-doc Martin K. Petersen
2024-04-12 2:05 ` 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=171288602656.3729249.13953839600529757224.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=bvanassche@acm.org \
--cc=corbet@lwn.net \
--cc=dgilbert@interlog.com \
--cc=hare@suse.de \
--cc=jejb@linux.ibm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mgurtovoy@nvidia.com \
--cc=rdunlap@infradead.org \
--cc=sagi@grimberg.me \
--cc=target-devel@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).