From: Dan Williams <dan.j.williams@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Randy Dunlap <rdunlap@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
kernel test robot <lkp@intel.com>,
Joao Martins <joao.m.martins@oracle.com>, X86 ML <x86@kernel.org>,
Linux MM <linux-mm@kvack.org>,
linux-nvdimm <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH] x86/mm: Fix phys_to_target_node() export
Date: Tue, 3 Nov 2020 17:49:13 -0800 [thread overview]
Message-ID: <CAPcyv4jD15=Xeer-dOKy3oYOLQBouN70s2vsaKYponh_c+8-yw@mail.gmail.com> (raw)
In-Reply-To: <20201103173816.8f80920621fe08012deacfcc@linux-foundation.org>
On Tue, Nov 3, 2020 at 5:38 PM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Mon, 2 Nov 2020 15:52:39 -0800 Dan Williams <dan.j.williams@intel.com> wrote:
>
> > The attached patch is going through some kbuild-robot exposure to make
> > sure I did not break anything else.
>
> I'll duck this for now - please send it along formally if/when testing
> is successful.
Yeah, the robots are angry, some reworks needed.
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
prev parent reply other threads:[~2020-11-04 1:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 2:29 [PATCH] x86/mm: Fix phys_to_target_node() export Dan Williams
2020-10-30 3:05 ` Randy Dunlap
2020-10-30 11:34 ` David Hildenbrand
2020-10-31 1:54 ` Dan Williams
2020-10-31 3:01 ` Thomas Gleixner
2020-10-31 4:45 ` Dan Williams
2020-10-31 9:10 ` Christoph Hellwig
2020-11-02 23:52 ` Dan Williams
2020-11-03 0:59 ` Randy Dunlap
2020-11-03 8:33 ` Christoph Hellwig
2020-11-03 10:39 ` Thomas Gleixner
2020-11-04 1:38 ` Andrew Morton
2020-11-04 1:49 ` Dan Williams [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='CAPcyv4jD15=Xeer-dOKy3oYOLQBouN70s2vsaKYponh_c+8-yw@mail.gmail.com' \
--to=dan.j.williams@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=joao.m.martins@oracle.com \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=lkp@intel.com \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).