From: Mike Rapoport <rppt@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
Fenghua Yu <fenghua.yu@intel.com>,
Michal Simek <michal.simek@xilinx.com>,
Michal Simek <monstr@monstr.eu>,
Randy Dunlap <rdunlap@infradead.org>,
Tony Luck <tony.luck@intel.com>,
kernel test robot <lkp@intel.com>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: [GIT PULL] Fix min_low_pfn/max_low_pfn build errors on ia64 and microblaze
Date: Thu, 3 Sep 2020 17:54:38 +0300 [thread overview]
Message-ID: <20200903145438.GA1781636@kernel.org> (raw)
Hi Linus,
The following changes since commit f75aef392f869018f78cfedf3c320a6b3fcfda6b:
Linux 5.9-rc3 (2020-08-30 16:01:54 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock.git tags/fixes-2020-09-03
for you to fetch changes up to 5f7b81c18366c38446f6eedab570b98dbdc07cff:
ia64: fix min_low_pfn/max_low_pfn build errors (2020-09-01 19:34:11 +0300)
----------------------------------------------------------------
Fix min_low_pfn/max_low_pfn build errors on ia64 and microblaze
Some configurations of ia64 and microblaze use min_low_pfn and
max_low_pfn in pfn_valid(). This causes build failures for modules that
use pfn_valid().
The fix is to add EXPORT_SYMBOL() for these variables on ia64 and
microblaze.
----------------------------------------------------------------
Randy Dunlap (2):
microblaze: fix min_low_pfn/max_low_pfn build errors
ia64: fix min_low_pfn/max_low_pfn build errors
arch/ia64/kernel/ia64_ksyms.c | 2 +-
arch/microblaze/mm/init.c | 3 +++
2 files changed, 4 insertions(+), 1 deletion(-)
--
Sincerely yours,
Mike.
next reply other threads:[~2020-09-03 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 14:54 Mike Rapoport [this message]
2020-09-03 17:09 ` pr-tracker-bot
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=20200903145438.GA1781636@kernel.org \
--to=rppt@kernel.org \
--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=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=rdunlap@infradead.org \
--cc=rientjes@google.com \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.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