stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: gregkh@linuxfoundation.org, dan.j.williams@intel.com,
	snitzer@redhat.com, toshi.kani@hpe.com, stable@vger.kernel.org
Subject: Re: [v4.17-stable 0/5] Fix DM DAX handling
Date: Tue, 3 Jul 2018 15:42:39 -0600	[thread overview]
Message-ID: <20180703214239.GA10812@linux.intel.com> (raw)
In-Reply-To: <20180702202028.24726-1-ross.zwisler@linux.intel.com>

On Mon, Jul 02, 2018 at 02:20:23PM -0600, Ross Zwisler wrote:
> This is a v4.17-stable backport of my "Fix DM DAX handling" series which
> had backport collisions.
> 
> Greg, please let me know if I need to adjust anything in my backport
> formatting.

Oops, just noticed that one of the commit IDs I referenced was from a dev
branch and not upstream.  I'll fix that up, correct my upstream commit ID
formatting and sent out a v2.

      parent reply	other threads:[~2018-07-03 21:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-02 20:20 [v4.17-stable 0/5] Fix DM DAX handling Ross Zwisler
2018-07-02 20:20 ` [v4.17-stable 1/5] fs: allow per-device dax status checking for filesystems Ross Zwisler
2018-07-02 20:20 ` [v4.17-stable 2/5] dax: change bdev_dax_supported() to support boolean returns Ross Zwisler
2018-07-02 20:20 ` [v4.17-stable 3/5] pmem: only set QUEUE_FLAG_DAX for fsdax mode Ross Zwisler
2018-07-02 20:20 ` [v4.17-stable 4/5] dax: bdev_dax_supported() check for QUEUE_FLAG_DAX Ross Zwisler
2018-07-02 20:20 ` [v4.17-stable 5/5] dm: prevent DAX mounts if not supported Ross Zwisler
2018-07-03 21:42 ` Ross Zwisler [this message]

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=20180703214239.GA10812@linux.intel.com \
    --to=ross.zwisler@linux.intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=snitzer@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=toshi.kani@hpe.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).