From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: linux-nvdimm@lists.01.org
Subject: Re: [PATCH] dax: pgoff in fs DAX trace needs to be corrected
Date: Tue, 24 Jan 2017 11:33:39 -0700 [thread overview]
Message-ID: <20170124183339.GB28860@linux.intel.com> (raw)
In-Reply-To: <148521639917.25631.6919429328589810158.stgit@djiang5-desk3.ch.intel.com>
On Mon, Jan 23, 2017 at 05:06:39PM -0700, Dave Jiang wrote:
> With only vmf being passed in, the pgoff in vmf that is passed in is for
> the PTE and not the PMD. Fix up so the pgoff is corrected.
>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
Yep, this seems right to me. Thanks for catching it.
Reviewed-by: Ross Zwisler <ross.zwisler@linux.intel.com>
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
prev parent reply other threads:[~2017-01-24 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 0:06 [PATCH] dax: pgoff in fs DAX trace needs to be corrected Dave Jiang
2017-01-24 18:33 ` 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=20170124183339.GB28860@linux.intel.com \
--to=ross.zwisler@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=linux-nvdimm@lists.01.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