From: Matthew Wilcox <willy@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: rong.a.chen@intel.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
lkp@01.org
Subject: Re: [LKP] [xarray] 0e9446c35a: WARNING:at_include/linux/xarray.h:#xa_mk_value
Date: Mon, 5 Nov 2018 14:08:47 -0800 [thread overview]
Message-ID: <20181105220847.GA16465@bombadil.infradead.org> (raw)
In-Reply-To: <20181105180004.GA4923@bombadil.infradead.org>
On Mon, Nov 05, 2018 at 10:00:04AM -0800, Matthew Wilcox wrote:
> On Mon, Nov 05, 2018 at 09:57:47AM -0800, Linus Torvalds wrote:
> > Should that part of the test be surrounded by #ifdef CONFIG_64BIT? Or
> > did you _want_ the warnings?
>
> I should have just made that (1 << 24) instead of UINT_MAX. I had forgotten
> about 32-bit machines while writing that test.
>
> That prompted me to actually build the test suite on 32-bit and there's
> a few other things in there that want fixing. I'll have a pull request
> for you later today.
I've pushed out an update to
http://git.infradead.org/users/willy/linux-dax.git/shortlog/refs/heads/xarray
Let's give the automated testers a couple of days to chew on this before
I send you a real pull request? The last two commits are today's work
while the other commits have been stewing in the xarray-conv branch for
the last 2-3 weeks while I've been busily converting all the radix trees
and some of the IDRs to the XArray.
They say no battle plan survives contact with the enemy ... no API
survives contact with its users.
next prev parent reply other threads:[~2018-11-05 22:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 7:03 [LKP] [xarray] 0e9446c35a: WARNING:at_include/linux/xarray.h:#xa_mk_value kernel test robot
2018-11-05 17:57 ` Linus Torvalds
2018-11-05 18:00 ` Matthew Wilcox
2018-11-05 22:08 ` Matthew Wilcox [this message]
2018-11-05 22:15 ` Linus Torvalds
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=20181105220847.GA16465@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=rong.a.chen@intel.com \
--cc=torvalds@linux-foundation.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