[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180420113404.GZ17484@dhcp22.suse.cz>
Date: Fri, 20 Apr 2018 13:34:04 +0200
From: Michal Hocko <mhocko@...nel.org>
To: Stefan Agner <stefan@...er.ch>
Cc: Matthew Wilcox <willy@...radead.org>, akpm@...ux-foundation.org,
catalin.marinas@....com, torvalds@...ux-foundation.org,
pasha.tatashin@...cle.com, ard.biesheuvel@...aro.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] treewide: use PHYS_ADDR_MAX to avoid type casting
ULLONG_MAX
On Fri 20-04-18 13:20:10, Stefan Agner wrote:
> On 20.04.2018 13:15, Matthew Wilcox wrote:
> > 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.
>
> The patch "mm/memblock: introduce PHYS_ADDR_MAX" got merged earlier this
> week, should be in the -mm tree.
Andrew hasn't released his mmotm tree yet so this is not in linux-next
yet as well.
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists