public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	target-devel <target-devel@vger.kernel.org>,
	"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
	Sagi Grimberg <sagi@grimberg.me>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH] scsi: fix iscsi-related kernel-doc warnings
Date: Wed, 03 Jan 2018 23:11:48 -0500	[thread overview]
Message-ID: <yq1373mxny3.fsf@oracle.com> (raw)
In-Reply-To: <44a0f532-b1e9-e0cf-4a61-d592a4306f61@infradead.org> (Randy Dunlap's message of "Fri, 22 Dec 2017 14:08:27 -0800")


Randy,

> Fix kernel-doc warnings in drivers/scsi/ that are related to iscsi
> support interfaces.
>
> Fixes these kernel-doc warnings: (tested by adding these files to a new
> target.rst documentation file: WIP)

Applied to 4.16/scsi-queue, thanks!

> Cc:	"Nicholas A. Bellinger" <nab@linux-iscsi.org>
> Cc:	linux-scsi@vger.kernel.org
> Cc:	target-devel@vger.kernel.org
> Cc:	Sagi Grimberg <sagi@grimberg.me>
> Cc:	linux-rdma@vger.kernel.org
> Cc:	"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>
> Cc:	"Martin K. Petersen" <martin.petersen@oracle.com>

     ^^^ checkpatch complains about these spaces.

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2018-01-04  4:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-22 22:08 [PATCH] scsi: fix iscsi-related kernel-doc warnings Randy Dunlap
2018-01-04  4:11 ` Martin K. Petersen [this message]
     [not found]   ` <yq1373mxny3.fsf-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2018-01-04  5:58     ` Randy Dunlap

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=yq1373mxny3.fsf@oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nab@linux-iscsi.org \
    --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