From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Matthew Wilcox <willy@infradead.org>,
linux-mm <linux-mm@kvack.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] XArray for 4.19
Date: Fri, 24 Aug 2018 15:25:41 +1000 [thread overview]
Message-ID: <20180824152541.3553a8cc@canb.auug.org.au> (raw)
In-Reply-To: <CA+55aFxFjAmrFpwQmEHCthHOzgidCKnod+cNDEE+3Spu9o1s3w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 447 bytes --]
Hi Linus,
On Tue, 21 Aug 2018 19:09:31 -0700 Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> For some unfathomable reason, you have based it on the libnvdimm tree.
> I don't understand at all wjhy you did that.
That was partly my fault for giving not very good advice when the
(quite complex) merge conflict turned up in the linux-next tree. I
will try to give better advice in the future.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-08-24 5:25 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
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 [this message]
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
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=20180824152541.3553a8cc@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.org \
--cc=willy@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).