From: Linus Torvalds <email@example.com>
To: Matthew Wilcox <firstname.lastname@example.org>
Cc: linux-mm <email@example.com>,
Linux Kernel Mailing List <firstname.lastname@example.org>
Subject: Re: [GIT PULL] XArray for 4.19
Date: Tue, 21 Aug 2018 19:09:31 -0700 [thread overview]
Message-ID: <CA+55aFxFjAmrFpwQmEHCthHOzgidCKnod+cNDEE+3Spu9o1s3w@mail.gmail.com> (raw)
On Mon, Aug 13, 2018 at 9:14 AM Matthew Wilcox <email@example.com> wrote:
> Please consider pulling the XArray patch set.
So this merge window has been horrible, but I was just about to start
looking at it.
And no. I'm not going to pull this.
For some unfathomable reason, you have based it on the libnvdimm tree.
I don't understand at all wjhy you did that.
That libnvdimm tree didn't get merged., because it had complete
garbage in the mm/ code. And yes, that buggy shit was what you based
the radix tree code on.
I seriously have no idea why you have based it on some unstable random
tree in the first place.
But basing it on something that I independently refused to pull
because of obvious bugs from just a quick scan - that completely
invalidates this pull request.
I guess it makes this merge window easier, since now I don't even have
to look at the code, but it annoys the hell out of me when things like
There wasn't even a mention in the pull request about how this was all
based on some libnvdimm code that hadn't been merged yet.
But you must have known that, since you must have explicitly done the
pull request not against my tree, but against the bogus base branch.
And since I won't be merging this, I clearly won't be merging your
other pull request that depended on this either.
Why the f*ck were these features so interlinked to begin with?
next prev parent reply other threads:[~2018-08-22 2:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 16:13 [GIT PULL] XArray for 4.19 Matthew Wilcox
2018-08-22 2:09 ` Linus Torvalds [this message]
2018-08-22 2:50 ` Matthew Wilcox
2018-08-22 3:00 ` Linus Torvalds
2018-08-22 18:23 ` Matthew Wilcox
2018-08-22 18:41 ` Linus Torvalds
2018-08-24 5:25 ` Stephen Rothwell
2018-08-22 17:40 ` Christopher Lameter
2018-08-22 17:43 ` Linus Torvalds
2018-08-22 18:23 ` Dan Williams
2018-08-24 13:21 ` Vlastimil Babka
2018-08-24 14:12 ` Christopher Lameter
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).