mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Stefan Agner <stefan@agner.ch>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Mark Salter <msalter@redhat.com>,
	Kees Cook <keescook@chromium.org>,
	Laura Abbott <lauraa@codeaurora.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v4] ARM: early fixmap support for earlycon
Date: Tue, 16 Jun 2015 23:32:58 +0100	[thread overview]
Message-ID: <20150616223258.GW7557@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1434491507-6208-1-git-send-email-stefan@agner.ch>

On Tue, Jun 16, 2015 at 11:51:47PM +0200, Stefan Agner wrote:
> Add early fixmap support, initially to support permanent, fixed
> mapping support for early console. A temporary, early pte is
> created which is migrated to a permanent mapping in paging_init.
> This is also needed since the attributes may change as the memory
> types are initialized. The 3MiB range of fixmap spans two pte
> tables, but currently only one pte is created for early fixmap
> support.
> 
> Re-add FIX_KMAP_BEGIN to the index calculation in highmem.c since
> the index for kmap does not start at zero anymore. This reverts
> 4221e2e6b316 ("ARM: 8031/1: fixmap: remove FIX_KMAP_BEGIN and
> FIX_KMAP_END") to some extent.

Sorry, this isn't going to make the next merge window, I've closed my
tree at the end of last week to new submissions (because it got too
painful to maintain the for-next branch due to the number of cross-
dependencies between branches.)  The only patches I'll entertain this
week and throughout the merge window are bug fixes.

-- 
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2015-06-16 22:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16 21:51 Stefan Agner
2015-06-16 22:32 ` Russell King - ARM Linux [this message]
2015-06-17 11:43   ` Stefan Agner
2015-06-17 19:43     ` Russell King - ARM Linux
2015-07-06  6:45       ` Stefan Agner
2015-06-16 23:22 ` Stephen Boyd
2015-06-17  9:33   ` Ard Biesheuvel
2015-06-30 12:33 ` Heiko Stübner
2015-07-30 21:02 ` Stefan Agner
2015-08-08 17:53   ` Russell King - ARM Linux

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=20150616223258.GW7557@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=ard.biesheuvel@linaro.org \
    --cc=arnd@arndb.de \
    --cc=keescook@chromium.org \
    --cc=lauraa@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msalter@redhat.com \
    --cc=robh@kernel.org \
    --cc=stefan@agner.ch \
    /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

all inboxes | Powered by JetHome®