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 22:22:12 +0000 [thread overview]
Message-ID: <20111207222212.GG14542@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAHkRjk7H+A4XKk+==hKPGdnUfaS4PePEf9-p-iO6eE=+xOmTWw@mail.gmail.com>
On Wed, Dec 07, 2011 at 10:15:24PM +0000, Catalin Marinas wrote:
> On 7 December 2011 20:29, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > On Wed, Dec 07, 2011 at 12:25:44PM +0000, Catalin Marinas wrote:
> >> ARM: pgtable: Fix compiler warning in ioremap.c introduced by nopud
> >>
> >> From: Catalin Marinas <catalin.marinas@arm.com>
> >>
> >> With the arch/arm code conversion to pgtable-nopud.h, the section and
> >> supersection (un|re)map code triggers compiler warnings on UP systems.
> >> This is caused by pmd_offset() being given a pgd_t argument rather than
> >> a pud_t one. This patch makes the necessary conversion via pud_alloc()
> >> and pmd_alloc().
> >>
> >> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
> >
> > So, do I now take this email as you saying that _your_ LPAE tree is
> > not ready for merging because you want to rework this patch, or what?
>
> No, I'm not, it's you saying that your nopud patch does not have any
> fix for the warnings, even though I had fixes posted for months.
Stop it Catalin. You're being utterly rediculous. You asked why I
hadn't merged my patch during the last merge window. So I told you -
just like I've been telling you by email and during our monthly calls
why I've not been merging it. You asked the question (again) so I
told you why (again).
> The
> same fix that's in my LPAE series was sent to you to include with your
> patch but instead you kept saying (even twice in the past week) that
> those warning had no fix.
Utter rubbish. I'll say it again. You asked why I hadn't merged my
patch. So I told you - just like I've been telling you by email and
during our monthly calls why I've not been merging it. You asked the
question (again) so I told you why.
> From that, I understand that you really
> don't consider my patch a proper fix for the compiler warnings.
WTF.
> > Because you've decided to go down the path of reworking this patch,
> > I consider it dangerous for me to just pull from your tree again - I've
> > no idea what I'd get, and I've no idea whether what's there is what you
> > want me to merge.
>
> I haven't changed anything in my LPAE branch, just posted an
> alternative fix-up for the nopud patch. Please _state_ clearly whether
> you consider my original (in the LPAE series) fixup valid or not. If
> yes, I'm happy that I don't have to rework anything.
Oh for god sake. I think I've already stated very clearly what I want.
I see no reason to repeat myself yet again.
next prev parent reply other threads:[~2011-12-07 22:22 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 [this message]
2011-12-08 0:16 ` Russell King - ARM Linux
2011-12-07 20:10 ` 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=20111207222212.GG14542@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).