[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d91c35be6f85a20028910babb35243d0@agner.ch>
Date: Fri, 20 Apr 2018 13:20:10 +0200
From: Stefan Agner <stefan@...er.ch>
To: Matthew Wilcox <willy@...radead.org>
Cc: akpm@...ux-foundation.org, mhocko@...e.com,
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 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.
--
Stefan
Powered by blists - more mailing lists