From: Christoph Hellwig <hch@infradead.org>
To: "Wu, Dennis" <dennis.wu@intel.com>
Cc: Christoph Hellwig <hch@infradead.org>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"nvdimm@lists.linux.dev" <nvdimm@lists.linux.dev>,
"Verma, Vishal L" <vishal.l.verma@intel.com>,
"Jiang, Dave" <dave.jiang@intel.com>,
"Weiny, Ira" <ira.weiny@intel.com>
Subject: Re: [PATCH] ACPI/NFIT: Add no_deepflush param to dynamic control flush operation
Date: Tue, 20 Sep 2022 04:46:08 -0700 [thread overview]
Message-ID: <YymoAGbaU7tOo0Lv@infradead.org> (raw)
In-Reply-To: <SN6PR11MB2640AC955668C96D5664F10BF84C9@SN6PR11MB2640.namprd11.prod.outlook.com>
On Tue, Sep 20, 2022 at 03:08:03AM +0000, Wu, Dennis wrote:
> Hi, Dan,
> Will we add this patch to some new kernel version?
How about addressing my comments and explaining what the exact
data integrity model is here first?
next prev parent reply other threads:[~2022-09-20 11:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 8:31 [PATCH] ACPI/NFIT: Add no_deepflush param to dynamic control flush operation Dennis.Wu
2022-06-29 15:27 ` Christoph Hellwig
2022-07-13 1:25 ` Dan Williams
2022-07-20 6:24 ` Christoph Hellwig
2022-09-20 3:08 ` Wu, Dennis
2022-09-20 11:46 ` Christoph Hellwig [this message]
2022-09-20 19:30 ` Dan Williams
2022-10-20 6:23 ` Wu, Dennis
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=YymoAGbaU7tOo0Lv@infradead.org \
--to=hch@infradead.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dennis.wu@intel.com \
--cc=ira.weiny@intel.com \
--cc=nvdimm@lists.linux.dev \
--cc=vishal.l.verma@intel.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