From: Thomas Gleixner <tglx@linutronix.de>
To: Dan Williams <dan.j.williams@intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
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: Sat, 31 Oct 2020 04:01:51 +0100 [thread overview]
Message-ID: <87blgjksio.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CAPcyv4iw_ZuHdhrGHUPh+iBYuO7sN_omEGb8RMmOKVzSCpbT0g@mail.gmail.com>
On Fri, Oct 30 2020 at 18:54, Dan Williams wrote:
> Thomas, do you want to ack this so Andrew can pick it up, or I can
> take it through as a device-dax update, but either way the diffstat
> warrants x86 + mm acks.
It's butt ugly but I couldn't come up with anything better right
away. So, FWIW:
Acked-by: Thomas Gleixner <tglx@linutronix.de>
Tested-by: Thomas Gleixner <tglx@linutronix.de>
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Gleixner <tglx@linutronix.de>
To: Dan Williams <dan.j.williams@intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
kernel test robot <lkp@intel.com>,
Joao Martins <joao.m.martins@oracle.com>, X86 ML <x86@kernel.org>,
Vishal Verma <vishal.l.verma@intel.com>,
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: Sat, 31 Oct 2020 04:01:51 +0100 [thread overview]
Message-ID: <87blgjksio.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CAPcyv4iw_ZuHdhrGHUPh+iBYuO7sN_omEGb8RMmOKVzSCpbT0g@mail.gmail.com>
On Fri, Oct 30 2020 at 18:54, Dan Williams wrote:
> Thomas, do you want to ack this so Andrew can pick it up, or I can
> take it through as a device-dax update, but either way the diffstat
> warrants x86 + mm acks.
It's butt ugly but I couldn't come up with anything better right
away. So, FWIW:
Acked-by: Thomas Gleixner <tglx@linutronix.de>
Tested-by: Thomas Gleixner <tglx@linutronix.de>
next prev parent reply other threads:[~2020-10-31 3:01 UTC|newest]
Thread overview: 26+ 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 2:29 ` Dan Williams
2020-10-30 3:05 ` Randy Dunlap
2020-10-30 3:05 ` Randy Dunlap
2020-10-30 11:34 ` David Hildenbrand
2020-10-30 11:34 ` David Hildenbrand
2020-10-31 1:54 ` Dan Williams
2020-10-31 1:54 ` Dan Williams
2020-10-31 3:01 ` Thomas Gleixner [this message]
2020-10-31 3:01 ` Thomas Gleixner
2020-10-31 4:45 ` Dan Williams
2020-10-31 4:45 ` Dan Williams
2020-10-31 9:10 ` Christoph Hellwig
2020-10-31 9:10 ` Christoph Hellwig
2020-11-02 23:52 ` Dan Williams
2020-11-02 23:52 ` Dan Williams
2020-11-03 0:59 ` Randy Dunlap
2020-11-03 0:59 ` Randy Dunlap
2020-11-03 8:33 ` Christoph Hellwig
2020-11-03 8:33 ` Christoph Hellwig
2020-11-03 10:39 ` Thomas Gleixner
2020-11-03 10:39 ` Thomas Gleixner
2020-11-04 1:38 ` Andrew Morton
2020-11-04 1:38 ` Andrew Morton
2020-11-04 1:49 ` Dan Williams
2020-11-04 1:49 ` 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=87blgjksio.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--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=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.