From: Linus Torvalds <torvalds@linux-foundation.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: "Luck, Tony" <tony.luck@intel.com>,
Andrea Arcangeli <aarcange@redhat.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-arch@vger.kernel.org
Subject: Re: ia64 broken by transparent huge pages - other arches too?
Date: Sun, 16 Jan 2011 13:05:15 -0800 [thread overview]
Message-ID: <AANLkTikZ+MmM9f0tidpccDAimtUkDvJ3N=3KE+xFxc63@mail.gmail.com> (raw)
In-Reply-To: <1295076096.4875.60.camel@pasglop>
On Fri, Jan 14, 2011 at 11:21 PM, Benjamin Herrenschmidt
<benh@kernel.crashing.org> wrote:
>
> This is insane. Having such a massively invasive change to the whole mm,
> barely tested on most architecture, and last I heard still generally
> controversial being merged like that without even some integration
> testing via -next makes no sense.
>
> Linus, wtf is going on ?
I pretty much take anything from Andrew, unless I hate it (and the
latest version of the transparent huge-page was ok).
That said, I did think that Andrew's -mm tree was in -next, and there
clearly is some serious problem wrt -mm and -next if this wasn't
caught earlier there.
I was also expecting the fixups to come through Andrew, and they
haven't. I can apply whatever people agree is sane, but right now I
don't even know what the final patch for this problem is.
Linus
next prev parent reply other threads:[~2011-01-16 21:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 17:50 ia64 broken by transparent huge pages - other arches too? Luck, Tony
2011-01-14 17:50 ` Luck, Tony
2011-01-14 18:30 ` Andrea Arcangeli
2011-01-14 18:50 ` Tony Luck
2011-01-14 19:03 ` Andrea Arcangeli
2011-01-15 7:21 ` Benjamin Herrenschmidt
2011-01-15 15:59 ` Andrea Arcangeli
2011-01-15 16:47 ` James Bottomley
2011-01-15 17:23 ` Andrea Arcangeli
2011-01-15 19:02 ` Geert Uytterhoeven
2011-01-15 21:31 ` Benjamin Herrenschmidt
2011-01-16 21:05 ` Linus Torvalds [this message]
2011-01-16 21:10 ` Andrew Morton
2011-01-16 22:06 ` Andrea Arcangeli
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='AANLkTikZ+MmM9f0tidpccDAimtUkDvJ3N=3KE+xFxc63@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
/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).