Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755592AbbFQLqJ (ORCPT ); Wed, 17 Jun 2015 07:46:09 -0400 Received: from mail.kmu-office.ch ([178.209.48.109]:45447 "EHLO mail.kmu-office.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753414AbbFQLqB (ORCPT ); Wed, 17 Jun 2015 07:46:01 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Date: Wed, 17 Jun 2015 13:43:17 +0200 From: Stefan Agner To: Russell King - ARM Linux Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Mark Salter , Kees Cook , Laura Abbott , Arnd Bergmann , Ard Biesheuvel , Rob Herring Subject: Re: [PATCH v4] ARM: early fixmap support for earlycon In-Reply-To: <20150616223258.GW7557@n2100.arm.linux.org.uk> References: <1434491507-6208-1-git-send-email-stefan@agner.ch> <20150616223258.GW7557@n2100.arm.linux.org.uk> Message-ID: User-Agent: Roundcube Webmail/1.1.2 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1637 Lines: 34 On 2015-06-17 00:32, Russell King - ARM Linux wrote: > 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. Ok no problem, I guess it's anyway a good idea to add it early in the development cycle so the change gets a bit more testing coverage. Shall I rebase the patch just after the merge window and send it out again or add the patch in its current state to your patch tracker? -- Stefan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/