From: Pavel Tatashin <pasha.tatashin@oracle.com>
To: rppt@linux.vnet.ibm.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
mhocko@kernel.org, willy@infradead.org
Subject: Re: [PATCH] mm/memblock: replace u64 with phys_addr_t where appropriate
Date: Tue, 3 Jul 2018 13:22:52 -0400 [thread overview]
Message-ID: <CAGM2reZ1RWcUT67cTGcyB6UzUftyMyG7GTfp=XjNo5CN2=c_bg@mail.gmail.com> (raw)
In-Reply-To: <1530637506-1256-1-git-send-email-rppt@linux.vnet.ibm.com>
On Tue, Jul 3, 2018 at 1:05 PM Mike Rapoport <rppt@linux.vnet.ibm.com> wrote:
>
> Most functions in memblock already use phys_addr_t to represent a physical
> address with __memblock_free_late() being an exception.
>
> This patch replaces u64 with phys_addr_t in __memblock_free_late() and
> switches several format strings from %llx to %pa to avoid casting from
> phys_addr_t to u64.
>
> CC: Michal Hocko <mhocko@kernel.org>
> CC: Matthew Wilcox <willy@infradead.org>
> Signed-off-by: Mike Rapoport <rppt@linux.vnet.ibm.com>
Looks good.
Reviewed-by: Pavel Tatashin <pasha.tatashin@oracle.com>
One minor thing that I would like to change in memblock.c is the
useage phys_addr_t for size. I understand the reasoning behind this
choice, but could we do something like:
typedef phys_addr_t phys_size_t;
It would be similar to resource_size_t. I just think the code and
function prototypes would look better with proper typing.
Thank you,
Pavel
next prev parent reply other threads:[~2018-07-03 17:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 17:05 Mike Rapoport
2018-07-03 17:22 ` Pavel Tatashin [this message]
2018-07-03 19:57 ` Andrew Morton
2018-07-03 20:24 ` Joe Perches
2018-07-04 7:03 ` Mike Rapoport
2018-07-04 7:23 ` Sergey Senozhatsky
2018-07-04 9:04 ` Joe Perches
2018-07-04 9:20 ` Sergey Senozhatsky
2018-07-04 9:43 ` Sergey Senozhatsky
2018-07-04 15:20 ` Mike Rapoport
2018-07-04 7:54 ` Sergey Senozhatsky
2018-07-04 15:21 ` Mike Rapoport
2018-07-04 17:22 ` Joe Perches
2018-07-05 7:12 ` Mike Rapoport
2018-07-04 7:02 ` Mike Rapoport
2018-07-04 13:05 ` Michal Hocko
2018-07-04 13:24 ` Mike Rapoport
2018-07-04 13:29 ` Michal Hocko
2018-07-04 14:04 ` 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='CAGM2reZ1RWcUT67cTGcyB6UzUftyMyG7GTfp=XjNo5CN2=c_bg@mail.gmail.com' \
--to=pasha.tatashin@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=rppt@linux.vnet.ibm.com \
--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