public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Jason Gunthorpe <jgg@nvidia.com>
Subject: Re: [akpm-mm:mm-unstable 115/141] mm/gup.c:536:22: error: call to undeclared function 'pud_pfn'; ISO C99 and later do not support implicit function declarations
Date: Sat, 23 Mar 2024 13:38:44 -0400	[thread overview]
Message-ID: <Zf8TpI3unIxZuPRn@x1n> (raw)
In-Reply-To: <202403240112.kHKVSfCL-lkp@intel.com>

On Sun, Mar 24, 2024 at 01:24:25AM +0800, kernel test robot wrote:
> >> mm/gup.c:536:22: error: call to undeclared function 'pud_pfn'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
>      536 |         unsigned long pfn = pud_pfn(pud);
>          |                             ^
>    mm/gup.c:536:22: note: did you mean 'pte_pfn'?
>    arch/powerpc/include/asm/pgtable.h:60:29: note: 'pte_pfn' declared here
>       60 | static inline unsigned long pte_pfn(pte_t pte)
>          |                             ^
>    9 warnings and 1 error generated.

Duplicated issue of:

https://lore.kernel.org/r/202403231529.HRev1zcD-lkp@intel.com/

Resolved by:

https://lore.kernel.org/r/20240323151643.1047281-1-peterx@redhat.com

-- 
Peter Xu


      reply	other threads:[~2024-03-23 17:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-23 17:24 [akpm-mm:mm-unstable 115/141] mm/gup.c:536:22: error: call to undeclared function 'pud_pfn'; ISO C99 and later do not support implicit function declarations kernel test robot
2024-03-23 17:38 ` Peter Xu [this message]

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=Zf8TpI3unIxZuPRn@x1n \
    --to=peterx@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=jgg@nvidia.com \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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