From: Christoph Hellwig <hch@lst.de>
To: Bart Van Assche <bart.vanassche@sandisk.com>
Cc: James Bottomley <james.bottomley@hansenpartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@lst.de>,
Johannes Thumshirn <jthumshirn@suse.de>,
Dan Williams <dan.j.williams@intel.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Sebastian Herbszt <herbszt@gmx.de>
Subject: Re: [PATCH v2, RESEND] Separate target visibility from reaped state information
Date: Wed, 6 Jan 2016 13:16:09 +0100 [thread overview]
Message-ID: <20160106121609.GB21780@lst.de> (raw)
In-Reply-To: <568CCF4F.2000108@sandisk.com>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2016-01-06 12:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 8:24 [PATCH v2, RESEND] Separate target visibility from reaped state information Bart Van Assche
2016-01-06 12:16 ` Christoph Hellwig [this message]
2016-01-06 15:58 ` James Bottomley
2016-01-06 21:34 ` Sebastian Herbszt
2016-01-08 16:15 ` 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=20160106121609.GB21780@lst.de \
--to=hch@lst.de \
--cc=bart.vanassche@sandisk.com \
--cc=dan.j.williams@intel.com \
--cc=herbszt@gmx.de \
--cc=james.bottomley@hansenpartnership.com \
--cc=jthumshirn@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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;
as well as URLs for NNTP newsgroup(s).