stgt.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ronnie Sahlberg <ronniesahlberg@gmail.com>
To: stgt@vger.kernel.org
Cc: fujita.tomonori@lab.ntt.co.jp
Subject: [PATCH] Add WRITE_ATOMIC_16 support
Date: Thu, 10 Sep 2015 17:36:35 -0700	[thread overview]
Message-ID: <1441931796-20788-1-git-send-email-ronniesahlberg@gmail.com> (raw)


Tomo, All

Version 3 of the WRITE_ATOMIC_16 patch.

Changes since version 2:
* WriteAtomic with transfer-length == 0 is actually not an error.

Changes since version 1:
* Use msync( MS_SYNC|MS_ASYNC) depending on whether or not FUA is set or not.

             reply	other threads:[~2015-09-11  0:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-11  0:36 Ronnie Sahlberg [this message]
2015-09-11  0:36 ` [PATCH] Add support for WRITE_ATOMIC_16 Ronnie Sahlberg
  -- strict thread matches above, loose matches on Subject: below --
2015-09-10 12:58 [PATCH] Add WRITE_ATOMIC_16 support Ronnie Sahlberg
2015-09-09 18:43 Ronnie Sahlberg
2015-09-15  9:54 ` FUJITA Tomonori
2015-09-16 19:49   ` ronnie sahlberg
2015-09-23  3:16     ` FUJITA Tomonori

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=1441931796-20788-1-git-send-email-ronniesahlberg@gmail.com \
    --to=ronniesahlberg@gmail.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=stgt@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 read-only IMAP folder(s) and NNTP newsgroup(s).