From: Christoph Hellwig <hch@lst.de>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
Jaegeuk Kim <jaegeuk@kernel.org>,
linux-scsi@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Ming Lei <ming.lei@redhat.com>, Hannes Reinecke <hare@suse.de>,
John Garry <john.g.garry@oracle.com>,
Mike Christie <michael.christie@oracle.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>
Subject: Re: [PATCH 2/4] scsi: core: Update a source code comment
Date: Fri, 28 Apr 2023 07:38:17 +0200 [thread overview]
Message-ID: <20230428053817.GB8549@lst.de> (raw)
In-Reply-To: <20230425233446.1231000-3-bvanassche@acm.org>
Hi Bart, this is the first patch of the series I'm seeing in my
inbox. It seems like patch 1 and the cover letter got lost,
making a useful review impossible.
next prev parent reply other threads:[~2023-04-28 5:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 23:34 [PATCH 0/4] SCSI core patches Bart Van Assche
2023-04-25 23:34 ` [PATCH 1/4] scsi: core: Use min() instead of open-coding it Bart Van Assche
2023-04-25 23:34 ` [PATCH 2/4] scsi: core: Update a source code comment Bart Van Assche
2023-04-28 5:38 ` Christoph Hellwig [this message]
2023-04-28 16:58 ` Bart Van Assche
2023-04-25 23:34 ` [PATCH 3/4] scsi: Only kick the requeue list if necessary Bart Van Assche
2023-04-26 3:23 ` kernel test robot
2023-04-26 5:16 ` kernel test robot
2023-04-25 23:34 ` [PATCH 4/4] scsi: Trace SCSI sense data Bart Van Assche
2023-04-25 23:52 ` Steven Rostedt
2023-04-28 8:09 ` Niklas Cassel
2023-04-28 18:36 ` Bart Van Assche
2023-05-02 9:52 ` Niklas Cassel
2023-05-02 20:31 ` Bart Van Assche
2023-05-03 7:16 ` Niklas Cassel
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=20230428053817.GB8549@lst.de \
--to=hch@lst.de \
--cc=bvanassche@acm.org \
--cc=hare@suse.de \
--cc=jaegeuk@kernel.org \
--cc=jejb@linux.ibm.com \
--cc=john.g.garry@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox