From: Bart Van Assche <bvanassche@acm.org>
To: John Garry <john.garry@huawei.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org,
Bradley Grove <linuxdrivers@attotech.com>,
Christoph Hellwig <hch@lst.de>, Ming Lei <ming.lei@redhat.com>,
Hannes Reinecke <hare@suse.de>,
Mike Christie <michael.christie@oracle.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
"James E.J. Bottomley" <jejb@linux.ibm.com>
Subject: Re: [PATCH v4 2/4] scsi: esas2r: Introduce scsi_template_proc_dir()
Date: Wed, 14 Sep 2022 09:43:00 -0700 [thread overview]
Message-ID: <3ee85c43-161f-58a1-0319-8062547a630b@acm.org> (raw)
In-Reply-To: <d63c326b-fa17-694c-cb72-aa746919218c@huawei.com>
On 9/14/22 02:06, John Garry wrote:
> On 13/09/2022 20:57, Bart Van Assche wrote:
>> This patch does not change any functionality.
>
> ... intentionally :)
The above comment is not clear to me, nor whether any action is expected
from my side?
Thanks,
Bart.
next prev parent reply other threads:[~2022-09-14 16:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 19:57 [PATCH v4 0/4] Prepare for constifying SCSI host templates Bart Van Assche
2022-09-13 19:57 ` [PATCH v4 1/4] scsi: esas2r: Initialize two host template members implicitly Bart Van Assche
2022-09-14 9:05 ` John Garry
2022-09-13 19:57 ` [PATCH v4 2/4] scsi: esas2r: Introduce scsi_template_proc_dir() Bart Van Assche
2022-09-14 9:06 ` John Garry
2022-09-14 16:43 ` Bart Van Assche [this message]
2022-09-14 16:53 ` John Garry
2022-09-13 19:57 ` [PATCH v4 3/4] scsi: core: Introduce a new list for SCSI proc directory entries Bart Van Assche
2022-09-14 9:43 ` John Garry
2022-09-14 16:52 ` Bart Van Assche
2022-09-13 19:57 ` [PATCH v4 4/4] scsi: core: Rework the code for dropping the LLD module reference Bart Van Assche
2022-09-14 9:52 ` John Garry
2022-09-14 17:54 ` Bart Van Assche
2022-09-14 9:21 ` [PATCH v4 0/4] Prepare for constifying SCSI host templates John Garry
2022-09-14 17:06 ` Bart Van Assche
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=3ee85c43-161f-58a1-0319-8062547a630b@acm.org \
--to=bvanassche@acm.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jejb@linux.ibm.com \
--cc=john.garry@huawei.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxdrivers@attotech.com \
--cc=martin.petersen@oracle.com \
--cc=michael.christie@oracle.com \
--cc=ming.lei@redhat.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 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.