LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: benh@kernel.crashing.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [patch 2/3] CONFIG_HIGHPTE vs. sub-page page tables.
Date: Mon, 04 Feb 2008 11:36:49 +0100 [thread overview]
Message-ID: <1202121409.31801.7.camel@localhost> (raw)
In-Reply-To: <20080202215315.3ac6907d.akpm@linux-foundation.org>
On Sat, 2008-02-02 at 21:53 -0800, Andrew Morton wrote:
> On Sun, 03 Feb 2008 16:37:00 +1100 Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> > Why dropping add-mm-argument-to-pte-pmd-pud-pgd_free.patch though ?
>
> I dropped the whole series.
Sniff .. my patches .. ;-)
> > It's a sane patch and a helps going further, and a total pain to re-do
> > later on. Besides, I may have some use for it on powerpc at some point
> > too...
>
> OK, I'll try to reestablish it.
Fine. I've got the patch-merge message, so the first of the series is
done.
> Look: I can't fix *everyone's* stuff. This was a consequence of ongoing
> unbounded churn in the x86 tree. If we can find a way of preventing those
> guys (and everyone else) from trashing everyone else's stuff then we'd have
> much smoother sailing.
Understood. That is where I jump in and regenerate my patches on the
latest available level. That the patches did hold up for some months in
-mm now without really breaking anything is an indication that we can
push them upstream now, isn't ? That would make the patch problem go
away and I could queue my s390 specific page table rework. Our KVM
people keep asking about it.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2008-02-04 10:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 14:30 [patch 0/3] page table changes schwidefsky
2007-11-12 14:30 ` [patch 1/3] add mm argument to pte/pmd/pud/pgd_free schwidefsky
2007-11-12 14:30 ` [patch 2/3] CONFIG_HIGHPTE vs. sub-page page tables schwidefsky
2008-01-02 20:44 ` Christoph Hellwig
2008-01-02 21:24 ` Geert Uytterhoeven
2008-01-02 21:28 ` Benjamin Herrenschmidt
2008-01-03 13:12 ` Andi Kleen
2008-01-03 14:01 ` Boaz Harrosh
2008-02-01 23:15 ` Andrew Morton
2008-02-03 5:37 ` Benjamin Herrenschmidt
2008-02-03 5:53 ` Andrew Morton
2008-02-03 6:46 ` Ingo Molnar
2008-02-04 10:36 ` Martin Schwidefsky [this message]
2008-02-04 10:51 ` Andrew Morton
2008-02-04 11:02 ` Russell King
2008-02-04 11:14 ` Andrew Morton
2008-02-05 14:39 ` Martin Schwidefsky
2008-02-05 18:46 ` Andrew Morton
2008-02-06 9:06 ` Martin Schwidefsky
2008-02-06 9:09 ` Andrew Morton
2008-02-06 9:15 ` Ingo Molnar
2008-02-06 15:50 ` Martin Schwidefsky
2007-11-12 14:30 ` [patch 3/3] arch_rebalance_pgtables call schwidefsky
2007-11-13 12:33 ` Nick Piggin
2007-11-14 9:26 ` Martin Schwidefsky
2007-11-14 10:06 ` Benjamin Herrenschmidt
2007-11-14 11:49 ` Martin Schwidefsky
2007-11-14 22:07 ` Benjamin Herrenschmidt
2007-11-15 17:13 ` Martin Schwidefsky
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=1202121409.31801.7.camel@localhost \
--to=schwidefsky@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--subject='Re: [patch 2/3] CONFIG_HIGHPTE vs. sub-page page tables.' \
/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
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).