From: Jan Kara <jack@suse.cz>
To: Ted Tso <tytso@mit.edu>
Cc: Jan Kara <jack@suse.cz>,
linux-nvdimm@lists.01.org, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org
Subject: [PATCH 0/4] ext4: DAX fixes
Date: Wed, 11 May 2016 11:39:07 +0200 [thread overview]
Message-ID: <1462959551-28622-1-git-send-email-jack@suse.cz> (raw)
Hi!
These are ext4 patches that were originally part of my DAX locking patch
series. They stand on their own so I'm submitting them independently and since
they are non-trivial, I'd like them to be merged through ext4 tree. The rest
of the DAX locking series depends on these patches so whichever tree is going
to merge them will have to pull the ext4 tree to get these patches. They
didn't change since the last posting of the DAX locking series (except for
minor fixup due to patch reordering).
Ted, can you please queue these patches for the coming merge window? Thanks!
Honza
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kara <jack@suse.cz>
To: Ted Tso <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, linux-nvdimm@lists.01.org,
Vishal Verma <vishal.l.verma@intel.com>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
Dan Williams <dan.j.williams@intel.com>,
linux-fsdevel@vger.kernel.org, Jan Kara <jack@suse.cz>
Subject: [PATCH 0/4] ext4: DAX fixes
Date: Wed, 11 May 2016 11:39:07 +0200 [thread overview]
Message-ID: <1462959551-28622-1-git-send-email-jack@suse.cz> (raw)
Hi!
These are ext4 patches that were originally part of my DAX locking patch
series. They stand on their own so I'm submitting them independently and since
they are non-trivial, I'd like them to be merged through ext4 tree. The rest
of the DAX locking series depends on these patches so whichever tree is going
to merge them will have to pull the ext4 tree to get these patches. They
didn't change since the last posting of the DAX locking series (except for
minor fixup due to patch reordering).
Ted, can you please queue these patches for the coming merge window? Thanks!
Honza
next reply other threads:[~2016-05-11 9:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 9:39 Jan Kara [this message]
2016-05-11 9:39 ` [PATCH 0/4] ext4: DAX fixes Jan Kara
2016-05-11 9:39 ` [PATCH 1/4] ext4: Handle transient ENOSPC properly for DAX Jan Kara
2016-05-11 9:39 ` Jan Kara
2016-05-11 9:39 ` [PATCH 2/4] ext4: Fix race in transient ENOSPC detection Jan Kara
2016-05-11 9:39 ` Jan Kara
2016-05-11 9:39 ` [PATCH 3/4] ext4: Refactor direct IO code Jan Kara
2016-05-11 9:39 ` Jan Kara
2016-05-11 9:39 ` [PATCH 4/4] ext4: Pre-zero allocated blocks for DAX IO Jan Kara
2016-05-11 9:39 ` Jan Kara
2016-05-13 5:24 ` [PATCH 0/4] ext4: DAX fixes Theodore Ts'o
2016-05-13 13:56 ` Theodore Ts'o
2016-05-16 9:35 ` Jan Kara
2016-05-16 14:26 ` Jan Kara
2016-05-16 15:08 ` Theodore Ts'o
2016-05-16 15:13 ` Dan Williams
2016-05-16 15:59 ` Jan Kara
2016-05-16 18:29 ` Dan Williams
2016-05-16 20:47 ` Theodore Ts'o
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=1462959551-28622-1-git-send-email-jack@suse.cz \
--to=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=tytso@mit.edu \
/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.