From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Linux support for ARM LPAE
Date: Wed, 7 Dec 2011 20:10:21 +0000 [thread overview]
Message-ID: <20111207201021.GD14542@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20111207112320.GB23720@arm.com>
On Wed, Dec 07, 2011 at 11:23:20AM +0000, Catalin Marinas wrote:
> On Tue, Dec 06, 2011 at 11:30:58PM +0000, Russell King - ARM Linux wrote:
> > On Tue, Dec 06, 2011 at 02:07:29PM +0000, Catalin Marinas wrote:
> > > This patch wasn't
> > > originally part of my LPAE series as I hoped you would have merged it
> > > during the last cycle. Now it had to be part of the pull request as LPAE
> > > patches depend on it.
> >
> > I've stated many times why it's not merged, and for the N'th time: it
> > generates warnings. I'm _not_ merging something that is known to add
> > warnings such as those which this patch produces without there being a
> > fix for it. You know that _very well_ because I've said it several
> > times, not only by email but also on our various phone calls.
> >
> > I've dealt with this patch in exactly the same way at every merge window
> > we've had for the last _year_ - I've queued it up with the expectation
> > that hopefully someone would fix the warnings, the warnings didn't get
> > fixed, so it got dropped from the pull request. Immediately after the
> > merge window (which includes this) it gets reinstated back into
> > linux-next.
>
> Yes, I'm fully aware, and I sent you a fix-up in the past. I can
> re-write that fix-up in a few other ways if you don't like the current
> one, just let me know.
So you mean you're submitting me my patch that I've been avoiding merging
into mainline _without_ the fixup patch? It seems not - you do have it
in your pull request:
ARM: pgtable: Fix compiler warning in ioremap.c introduced by nopud
So what's the issue? Why do you want to rewrite it yet again?
My guess is that you haven't actually READ what I said above (which is
quoted). And what is quoted above is _me_ explaining _why_ I have not
merged my own patch and why _I_ _consider_ _the_ _patch_ _as_ _it_
_stands_ _to_ _not_ _be_ _immediately_ _suitable_ _for_ _merging_
___on___ ___its___ ___own___.
The fact is, with the "fix" patch, it _does_ become suitable for merging.
Are you getting the message yet?
Provided you've fixed the sign-off (which you say you have) the only
remaining problem is the conflict between your tree and Will's tree
which you actually require for LPAE to be buildable. Which, I'll point
out, I'm not looking at at the moment because I'm writing this email to
you this evening instead.
prev parent reply other threads:[~2011-12-07 20:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 18:20 [GIT PULL] Linux support for ARM LPAE Catalin Marinas
2011-12-06 12:41 ` Russell King - ARM Linux
2011-12-06 14:07 ` Catalin Marinas
2011-12-06 23:30 ` Russell King - ARM Linux
2011-12-07 11:23 ` Catalin Marinas
2011-12-07 12:25 ` Catalin Marinas
2011-12-07 20:29 ` Russell King - ARM Linux
2011-12-07 22:15 ` Catalin Marinas
2011-12-07 22:22 ` Russell King - ARM Linux
2011-12-08 0:16 ` Russell King - ARM Linux
2011-12-07 20:10 ` Russell King - ARM Linux [this message]
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=20111207201021.GD14542@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).