Re: [PATCH .36-rc8] arm: mm: allow, but warn, when issuingioremap() on RAM

[Russell King - ARM Linux]

On Sun, Oct 17, 2010 at 03:06:44PM +0300, Felipe Contreras wrote:
> On Fri, Oct 15, 2010 at 11:14 PM, Russell King - ARM Linux
> <linux@xxxxxxxxxxxxxxxx> wrote:
> > On Fri, Oct 15, 2010 at 11:00:40PM +0300, Felipe Contreras wrote:
> >> On Fri, Oct 15, 2010 at 10:42 PM, Russell King - ARM Linux
> >> <linux@xxxxxxxxxxxxxxxx> wrote:
> >> > As soon as the first ARM merge hits during the merge window, I'll be
> >> > restoring the 'always fail' behaviour.
> >>
> >> Ok, are you going to merge also your patch to use memblock for the
> >> initialization? Many drivers could certainly use that to fix the
> >> issue.
> >
> > There's a lot of work going on with memblock in x86-land which impacts
> > ARM and means major conflicts for that patch - I think first we'll have
> > to deal with the fallout from that (iow, finding out what's been broken
> > by this activity and fix that), and then I'll have to re-do my patch from
> > the beginning.
> >
> > Technically, following the rules, that means it has to miss this merge
> > window - so it looks like it's going to take another six months to solve
> > this issue (three months to get the memblock patch in, and another three
> > months for driver fixes to find their way through.)
> 
> I don't think that's a good idea. Drivers would not have a way to get
> fixed, even for .37.
> 
> Are these x86 changes in some branch?

Yes but I've no idea where they are, and neither do I know exactly what
they are - they've never been copied to me or the ARM lists.  I'll just
wait for them to appear via Linus' tree in this merge window, and as I
said above, then fix the resulting breakage from them.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/