linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v2 1/5] memblock test: fix implicit declaration of function 'virt_to_phys'
Date: Thu, 1 Aug 2024 09:09:14 +0300	[thread overview]
Message-ID: <ZqsmisgECjaCt92Z@kernel.org> (raw)
In-Reply-To: <20240801000739.lrgmokbbgvikrlkw@master>

On Thu, Aug 01, 2024 at 12:07:39AM +0000, Wei Yang wrote:
> On Mon, Jul 29, 2024 at 08:37:23AM +0300, Mike Rapoport wrote:
> >On Mon, Jul 29, 2024 at 01:47:21AM +0000, Wei Yang wrote:
> >> Commit 94ff46de4a73 ("memblock: Move late alloc warning down to phys
> >> alloc") introduce the usage of virt_to_phys(), which is not defined in
> >> memblock tests.
> >> 
> >> Define it in mm.h to fix the build error.
> >> 
> >> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
> >> 
> >> ---
> >> v2: move definition to mm.h
> >> ---
> >>  tools/include/linux/mm.h | 2 ++
> >>  1 file changed, 2 insertions(+)
> >> 
> >> diff --git a/tools/include/linux/mm.h b/tools/include/linux/mm.h
> >> index cad4f2927983..9db45c5d00fc 100644
> >> --- a/tools/include/linux/mm.h
> >> +++ b/tools/include/linux/mm.h
> >> @@ -20,6 +20,8 @@
> >>  #define pfn_to_page(pfn) ((void *)((pfn) * PAGE_SIZE))
> >>  
> >>  #define phys_to_virt phys_to_virt
> >> +#define virt_to_phys(p) ((unsigned long)p)
> >> +
> >
> >Please don't break #define of phys_to_virt from the static inline
> >implementation.
> >
> 
> I don't touch the definition of phys_to_virt, so you are willing me to adjust
> it?
> 
> The macro here will be expanded to code at preprocessing stage. I don't get
> how static inline would help here. Do I miss something?

static inline allows type checking of the parameters and #define with the
same name as of the static inline allows catching other defines with the
same name.

So it's common practice to use this combination, line phys_to_virt does.
 
> >And please make virt_to_phys a static inline similarly to phys_to_virt.
> >
> >>  static inline void *phys_to_virt(unsigned long address)
> >>  {
> >>  	return __va(address);
> >> -- 
> >> 2.34.1
> >> 
> >
> >-- 
> >Sincerely yours,
> >Mike.
> 
> -- 
> Wei Yang
> Help you, Help me

-- 
Sincerely yours,
Mike.


  reply	other threads:[~2024-08-01  6:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29  1:47 [PATCH v2 1/5] memblock test: fix implicit declaration of function 'virt_to_phys' Wei Yang
2024-07-29  1:47 ` [PATCH v2 2/5] memblock test: add the definition of __setup() Wei Yang
2024-07-29  1:47 ` [PATCH v2 3/5] memblock test: fix implicit declaration of function 'memparse' Wei Yang
2024-07-29  1:47 ` [PATCH v2 4/5] memblock test: fix implicit declaration of function 'isspace' Wei Yang
2024-07-29  1:47 ` [PATCH v2 5/5] memblock test: fix implicit declaration of function 'strscpy' Wei Yang
2024-07-29  5:37 ` [PATCH v2 1/5] memblock test: fix implicit declaration of function 'virt_to_phys' Mike Rapoport
2024-08-01  0:07   ` Wei Yang
2024-08-01  6:09     ` Mike Rapoport [this message]
2024-08-02  0:53       ` Wei Yang

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=ZqsmisgECjaCt92Z@kernel.org \
    --to=rppt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=richard.weiyang@gmail.com \
    /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).