From mboxrd@z Thu Jan 1 00:00:00 1970 From: u.kleine-koenig@pengutronix.de (Uwe =?iso-8859-1?Q?Kleine-K=F6nig?=) Date: Fri, 11 Jul 2014 09:30:54 +0200 Subject: [GIT PULL v2] nommu fixes for 3.17-rc1 In-Reply-To: <20140701094159.GM14781@pengutronix.de> References: <20140630144355.GH14781@pengutronix.de> <20140701094159.GM14781@pengutronix.de> Message-ID: <20140711073054.GI11056@pengutronix.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Russell, On Tue, Jul 01, 2014 at 11:41:59AM +0200, Uwe Kleine-K?nig wrote: > Hello Russell, > > I updated my tag to pull to not include the commit that drops ARM740T, > ARM940T and ARM946E-S because of Arnd's concerns. Also the two cleanups > that depended on this one are dropped. > > (As before) I picked -rc3 as base because 1c2f87c22566..6980c3e2514e~ is > broken on nommu. > > The following changes since commit 4c834452aad01531db949414f94f817a86348d59: > > Linux 3.16-rc3 (2014-06-29 14:11:36 -0700) > > are available in the git repository at: > > git://git.pengutronix.de/git/ukl/linux.git tags/nommu-for-rmk > > for you to fetch changes up to 83de911cf897a4317147dd9cb379378c2c4abf4c: > > ARM: make user_addr_max more robust (2014-07-01 11:12:09 +0200) > > ---------------------------------------------------------------- > Two different fixes for the same problem making some ARM nommu configurations > not boot since 3.6-rc1. The problem is that user_addr_max returned the biggest > available RAM address which makes some copy_from_user variants fail to read > from XIP memory. > > Even in the presence of one of the two fixes the other still makes sense, so > both patches are included here. > > This problem was the last one preventing efm32 boot to a prompt with mainline. You neither commented nor pulled this request (at least I didn't find it in your repository). Is it still on your radar? Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-K?nig | Industrial Linux Solutions | http://www.pengutronix.de/ |