From: Matthew Wilcox <willy@infradead.org>
To: Stefan Agner <stefan@agner.ch>
Cc: akpm@linux-foundation.org, mhocko@suse.com,
catalin.marinas@arm.com, torvalds@linux-foundation.org,
pasha.tatashin@oracle.com, ard.biesheuvel@linaro.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] treewide: use PHYS_ADDR_MAX to avoid type casting ULLONG_MAX
Date: Fri, 20 Apr 2018 04:15:10 -0700 [thread overview]
Message-ID: <20180420111510.GA10788@bombadil.infradead.org> (raw)
In-Reply-To: <20180419214204.19322-1-stefan@agner.ch>
On Thu, Apr 19, 2018 at 11:42:04PM +0200, Stefan Agner wrote:
> With PHYS_ADDR_MAX there is now a type safe variant for all
> bits set. Make use of it.
There is? I don't see it in linux-next.
next prev parent reply other threads:[~2018-04-20 11:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 21:42 [PATCH] treewide: use PHYS_ADDR_MAX to avoid type casting ULLONG_MAX Stefan Agner
2018-04-20 7:58 ` Ard Biesheuvel
2018-04-20 9:49 ` Catalin Marinas
2018-04-20 11:15 ` Matthew Wilcox [this message]
2018-04-20 11:20 ` Stefan Agner
2018-04-20 11:34 ` Michal Hocko
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=20180420111510.GA10788@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=pasha.tatashin@oracle.com \
--cc=stefan@agner.ch \
--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;
as well as URLs for NNTP newsgroup(s).