From: Christoph Hellwig <hch@infradead.org>
To: Jane Chu <jane.chu@oracle.com>
Cc: nvdimm@lists.linux.dev, dave.jiang@intel.com, snitzer@redhat.com,
peterz@infradead.org, djwong@kernel.org, x86@kernel.org,
david@fromorbit.com, linux-kernel@vger.kernel.org,
willy@infradead.org, hch@infradead.org, dave.hansen@intel.com,
dm-devel@redhat.com, bp@alien8.de, vgoyal@redhat.com,
luto@kernel.org, vishal.l.verma@intel.com,
linux-fsdevel@vger.kernel.org, dan.j.williams@intel.com,
ira.weiny@intel.com, agk@redhat.com
Subject: Re: [dm-devel] [PATCH v9 4/7] dax: introduce DAX_RECOVERY_WRITE dax access mode
Date: Fri, 22 Apr 2022 22:20:49 -0700 [thread overview]
Message-ID: <YmOMsTyGhD73koYH@infradead.org> (raw)
In-Reply-To: <20220422224508.440670-5-jane.chu@oracle.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Jane Chu <jane.chu@oracle.com>
Cc: dan.j.williams@intel.com, bp@alien8.de, hch@infradead.org,
dave.hansen@intel.com, peterz@infradead.org, luto@kernel.org,
david@fromorbit.com, djwong@kernel.org,
linux-fsdevel@vger.kernel.org, nvdimm@lists.linux.dev,
linux-kernel@vger.kernel.org, x86@kernel.org,
vishal.l.verma@intel.com, dave.jiang@intel.com, agk@redhat.com,
snitzer@redhat.com, dm-devel@redhat.com, ira.weiny@intel.com,
willy@infradead.org, vgoyal@redhat.com
Subject: Re: [PATCH v9 4/7] dax: introduce DAX_RECOVERY_WRITE dax access mode
Date: Fri, 22 Apr 2022 22:20:49 -0700 [thread overview]
Message-ID: <YmOMsTyGhD73koYH@infradead.org> (raw)
In-Reply-To: <20220422224508.440670-5-jane.chu@oracle.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2022-04-23 5:42 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 22:45 [dm-devel] [PATCH v9 0/7] DAX poison recovery Jane Chu
2022-04-22 22:45 ` Jane Chu
2022-04-22 22:45 ` [dm-devel] [PATCH v9 1/7] acpi/nfit: rely on mce->misc to determine poison granularity Jane Chu
2022-04-22 22:45 ` Jane Chu
2022-04-22 22:45 ` [dm-devel] [PATCH v9 2/7] x86/mce: relocate set{clear}_mce_nospec() functions Jane Chu
2022-04-22 22:45 ` Jane Chu
2022-04-28 13:09 ` [dm-devel] " Borislav Petkov
2022-04-28 13:09 ` Borislav Petkov
2022-05-13 21:41 ` [PATCH v10 " Dan Williams
2022-05-16 18:21 ` [PATCH v11 " Dan Williams
2022-05-16 20:30 ` [dm-devel] [PATCH v9 " Dan Williams
2022-05-16 20:30 ` Dan Williams
2022-04-22 22:45 ` [dm-devel] [PATCH v9 3/7] mce: fix set_mce_nospec to always unmap the whole page Jane Chu
2022-04-22 22:45 ` Jane Chu
2022-04-22 23:25 ` [dm-devel] " Dan Williams
2022-04-22 23:25 ` Dan Williams
2022-05-11 3:56 ` [dm-devel] " Dan Williams
2022-05-11 3:56 ` Dan Williams
2022-05-11 8:44 ` [dm-devel] " Borislav Petkov
2022-05-11 8:44 ` Borislav Petkov
2022-05-11 17:17 ` [dm-devel] " Luck, Tony
2022-05-11 17:17 ` Luck, Tony
2022-05-13 3:41 ` [dm-devel] " Dan Williams
2022-05-13 3:41 ` Dan Williams
2022-05-16 18:38 ` [PATCH v10 " Dan Williams
2022-04-22 22:45 ` [dm-devel] [PATCH v9 4/7] dax: introduce DAX_RECOVERY_WRITE dax access mode Jane Chu
2022-04-22 22:45 ` Jane Chu
2022-04-23 5:20 ` Christoph Hellwig [this message]
2022-04-23 5:20 ` Christoph Hellwig
2022-05-13 21:55 ` [dm-devel] [PATCH v10 " Dan Williams
2022-05-13 21:55 ` Dan Williams
2022-05-13 22:09 ` [dm-devel] " Dan Williams
2022-05-13 22:09 ` Dan Williams
2022-05-13 22:10 ` [dm-devel] [PATCH v11 " Dan Williams
2022-05-13 22:10 ` Dan Williams
2022-05-16 12:40 ` [dm-devel] [PATCH v10 " Vivek Goyal
2022-05-16 12:40 ` Vivek Goyal
2022-04-22 22:45 ` [dm-devel] [PATCH v9 5/7] dax: add .recovery_write dax_operation Jane Chu
2022-04-22 22:45 ` Jane Chu
2022-04-22 22:45 ` [dm-devel] [PATCH v9 6/7] pmem: refactor pmem_clear_poison() Jane Chu
2022-04-22 22:45 ` Jane Chu
2022-04-22 22:45 ` [dm-devel] [PATCH v9 7/7] pmem: implement pmem_recovery_write() Jane Chu
2022-04-22 22:45 ` Jane Chu
2022-04-23 5:21 ` [dm-devel] " Christoph Hellwig
2022-04-23 5:21 ` Christoph Hellwig
2022-05-13 22:13 ` [PATCH v10 " Dan Williams
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=YmOMsTyGhD73koYH@infradead.org \
--to=hch@infradead.org \
--cc=agk@redhat.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave.jiang@intel.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=dm-devel@redhat.com \
--cc=ira.weiny@intel.com \
--cc=jane.chu@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=snitzer@redhat.com \
--cc=vgoyal@redhat.com \
--cc=vishal.l.verma@intel.com \
--cc=willy@infradead.org \
--cc=x86@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 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.