From: Juergen Gross <jgross@suse.com>
To: linux-kernel@vger.kernel.org, x86@kernel.org, hpa@zytor.com,
tglx@linutronix.de, mingo@redhat.com, linux-efi@vger.kernel.org,
matt.fleming@intel.com
Cc: Juergen Gross <jgross@suse.com>
Subject: [PATCH 0/4] x86: use correct early_[mem,io][re,un]map pairs
Date: Tue, 24 Feb 2015 10:13:27 +0100 [thread overview]
Message-ID: <1424769211-11378-1-git-send-email-jgross@suse.com> (raw)
Areas mapped via early_memremap() should be unmapped via
early_memunmap(), while I/O-areas should be mapped via early_ioremap()
and unmapped via early_iounmap().
There are multiple spots where an area is mapped via the mem variant
and unmapped via the io variant. This series corrects this by using
the appropriate variants.
Juergen Gross (4):
x86: use early_memunmap in arch/x86/kernel/devicetree.c
x86: use early_memunmap in arch/x86/kernel/e820.c
x86: use early_memunmap in arch/x86/kernel/setup.c
x86, efi: use early_ioremap in arch/x86/platform/efi/efi-bgrt.c
arch/x86/kernel/devicetree.c | 4 ++--
arch/x86/kernel/e820.c | 2 +-
arch/x86/kernel/setup.c | 8 ++++----
arch/x86/platform/efi/efi-bgrt.c | 4 ++--
4 files changed, 9 insertions(+), 9 deletions(-)
--
2.1.4
next reply other threads:[~2015-02-24 9:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 9:13 Juergen Gross [this message]
2015-02-24 9:13 ` [PATCH 1/4] x86: use early_memunmap in arch/x86/kernel/devicetree.c Juergen Gross
2015-02-24 9:13 ` [PATCH 2/4] x86: use early_memunmap in arch/x86/kernel/e820.c Juergen Gross
2015-02-24 9:13 ` [PATCH 3/4] x86: use early_memunmap in arch/x86/kernel/setup.c Juergen Gross
2015-02-24 9:13 ` [PATCH 4/4] x86, efi: use early_ioremap in arch/x86/platform/efi/efi-bgrt.c Juergen Gross
[not found] ` <1424769211-11378-1-git-send-email-jgross-IBi9RG/b67k@public.gmane.org>
2015-02-24 19:22 ` [PATCH 0/4] x86: use correct early_[mem,io][re,un]map pairs Matt Fleming
2015-02-26 7:50 ` Dave Young
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=1424769211-11378-1-git-send-email-jgross@suse.com \
--to=jgross@suse.com \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mingo@redhat.com \
--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