From: Christoph Hellwig <hch@infradead.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@fb.com>,
linux-scsi@vger.kernel.org, linux-nvme@lists.infradead.org,
dm-devel@redhat.com, linux-api@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Persistent Reservation API V3
Date: Wed, 26 Aug 2015 09:10:45 -0700 [thread overview]
Message-ID: <20150826161045.GA25123@infradead.org> (raw)
In-Reply-To: <1440605167-10769-1-git-send-email-hch@lst.de>
Meh, looks like the train wifi is too bad to send out a whole patch
series. I'll resend once I've arrived..
next prev parent reply other threads:[~2015-08-26 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 16:06 Persistent Reservation API V3 Christoph Hellwig
2015-08-26 16:10 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-26 16:56 Christoph Hellwig
[not found] ` <1440608214-14497-1-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
2015-08-29 1:33 ` Jeremy Linton
2015-08-29 13:52 ` Christoph Hellwig
2015-08-26 16:03 Christoph Hellwig
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=20150826161045.GA25123@infradead.org \
--to=hch@infradead.org \
--cc=axboe@fb.com \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@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 NNTP newsgroup(s).