From: Dan Williams <dan.j.williams@intel.com>
To: Davidlohr Bueso <dave@stgolabs.net>, <dan.j.williams@intel.com>
Cc: <x86@kernel.org>, <nvdimm@lists.linux.dev>,
<linux-cxl@vger.kernel.org>, <peterz@infradead.org>,
<bp@alien8.de>, <akpm@linux-foundation.org>,
<dave.jiang@intel.com>, <Jonathan.Cameron@huawei.com>,
<vishal.l.verma@intel.com>, <ira.weiny@intel.com>,
<a.manzanares@samsung.com>, <linux-kernel@vger.kernel.org>,
<hch@lst.de>
Subject: Re: [PATCH -next] memregion: Add arch_flush_memregion() interface
Date: Wed, 7 Sep 2022 09:46:17 -0700 [thread overview]
Message-ID: <6318cad97f5a1_166f294a7@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <20220907143603.d226eyi3uitlcmi5@offworld>
Davidlohr Bueso wrote:
> Not sure the proper way to route this (akpm?). But unless any remaining
> objections, could this be picked up?
My plan was, barring objections, to take it through the CXL tree with
its first user, the CXL security commands.
next prev parent reply other threads:[~2022-09-07 16:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 21:29 Davidlohr Bueso
2022-08-29 23:02 ` Dan Williams
2022-09-07 14:36 ` Davidlohr Bueso
2022-09-07 16:46 ` Dan Williams [this message]
2022-09-07 16:05 ` Borislav Petkov
2022-09-07 16:22 ` Davidlohr Bueso
2022-09-07 16:52 ` Dan Williams
2022-09-07 17:24 ` Davidlohr Bueso
2022-09-08 4:35 ` Borislav Petkov
2022-09-08 6:53 ` Dan Williams
2022-09-08 13:00 ` Jonathan Cameron
2022-09-08 4:31 ` Borislav Petkov
2022-09-07 22:30 ` Andrew Morton
2022-09-08 1:07 ` Dan Williams
2022-09-08 13:13 ` Jonathan Cameron
2022-09-08 22:51 ` Dan Williams
2022-09-08 23:00 ` Andrew Morton
2022-09-08 23:22 ` Dan Williams
2022-09-09 11:43 ` Jonathan Cameron
2022-09-13 15:56 ` Davidlohr Bueso
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=6318cad97f5a1_166f294a7@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=a.manzanares@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=hch@lst.de \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=vishal.l.verma@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®