All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	lkp <lkp@intel.com>, "linux-mm@kvack.org" <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	David Rientjes <rientjes@google.com>,
	"Yu, Fenghua" <fenghua.yu@intel.com>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>
Subject: RE: [PATCH] ia64: fix min_low_pfn/max_low_pfn build errors
Date: Tue, 01 Sep 2020 15:08:37 +0000	[thread overview]
Message-ID: <706c8eed209c4379baf2f1ac81b0112a@intel.com> (raw)
In-Reply-To: <20200901041902.GC424181@linux.ibm.com>

> I can take it via the memblock tree, would appreciate an Ack.

Thanks

Acked-by: Tony Luck <tony.luck@intel.com>

-Tony

WARNING: multiple messages have this Message-ID (diff)
From: "Luck, Tony" <tony.luck@intel.com>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	lkp <lkp@intel.com>, "linux-mm@kvack.org" <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	"David Rientjes" <rientjes@google.com>,
	"Yu, Fenghua" <fenghua.yu@intel.com>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>
Subject: RE: [PATCH] ia64: fix min_low_pfn/max_low_pfn build errors
Date: Tue, 1 Sep 2020 15:08:37 +0000	[thread overview]
Message-ID: <706c8eed209c4379baf2f1ac81b0112a@intel.com> (raw)
In-Reply-To: <20200901041902.GC424181@linux.ibm.com>

> I can take it via the memblock tree, would appreciate an Ack.

Thanks

Acked-by: Tony Luck <tony.luck@intel.com>

-Tony


  reply	other threads:[~2020-09-01 15:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-29  0:01 [PATCH] ia64: fix min_low_pfn/max_low_pfn build errors Randy Dunlap
2020-08-29  0:01 ` Randy Dunlap
2020-08-29 21:39 ` David Rientjes
2020-08-29 21:39   ` David Rientjes
2020-09-01  4:19 ` Mike Rapoport
2020-09-01  4:19   ` Mike Rapoport
2020-09-01 15:08   ` Luck, Tony [this message]
2020-09-01 15:08     ` Luck, Tony

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=706c8eed209c4379baf2f1ac81b0112a@intel.com \
    --to=tony.luck@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=fenghua.yu@intel.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=rdunlap@infradead.org \
    --cc=rientjes@google.com \
    --cc=rppt@linux.ibm.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 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.