From: David Hildenbrand <david@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>
Subject: Re: [akpm-mm:mm-new 101/118] arch/powerpc/mm/ptdump/shared.c:70:1: error: use of 'pgtable_level' with tag type that does not match previous declaration
Date: Tue, 12 Aug 2025 22:57:18 +0200 [thread overview]
Message-ID: <522f31cc-f250-4883-8832-0d26ebf5210b@redhat.com> (raw)
In-Reply-To: <0c96fa0e-6f7e-4cca-8d57-f3e3786d44fa@redhat.com>
On 12.08.25 22:50, David Hildenbrand wrote:
> On 12.08.25 21:18, kernel test robot wrote:
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-new
>> head: 33ad02f876604ac2990e510480b0ab3a03cf892e
>> commit: 627bf62489a6d9a45f6d6f83edd0cb6c0ee610c0 [101/118] mm/rmap: convert "enum rmap_level" to "enum pgtable_level"
>> config: powerpc-randconfig-001-20250812 (https://download.01.org/0day-ci/archive/20250813/202508130304.5FJqRz2c-lkp@intel.com/config)
>> compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
>> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250813/202508130304.5FJqRz2c-lkp@intel.com/reproduce)
>>
>> If you fix the issue in a separate patch/commit (i.e. not just a new version of
>> the same patch/commit), kindly add following tags
>> | Reported-by: kernel test robot <lkp@intel.com>
>> | Closes: https://lore.kernel.org/oe-kbuild-all/202508130304.5FJqRz2c-lkp@intel.com/
>>
>> All errors (new ones prefixed by >>):
>>
>> In file included from arch/powerpc/mm/ptdump/shared.c:10:
>> arch/powerpc/mm/ptdump/ptdump.h:14:1: error: use of 'pgtable_level' with tag type that does not match previous declaration
>> 14 | struct pgtable_level {
>> | ^
>> include/linux/pgtable.h:1961:6: note: previous use is here
>> 1961 | enum pgtable_level {
>> | ^
>> In file included from arch/powerpc/mm/ptdump/shared.c:10:
>> arch/powerpc/mm/ptdump/ptdump.h:20:8: error: use of 'pgtable_level' with tag type that does not match previous declaration
>> 20 | extern struct pgtable_level pg_level[5];
>> | ^
>> include/linux/pgtable.h:1961:6: note: previous use is here
>> 1961 | enum pgtable_level {
>> | ^
>>>> arch/powerpc/mm/ptdump/shared.c:70:1: error: use of 'pgtable_level' with tag type that does not match previous declaration
>> 70 | struct pgtable_level pg_level[5] = {
>> | ^
>> include/linux/pgtable.h:1961:6: note: previous use is here
>> 1961 | enum pgtable_level {
>> | ^
>> 3 errors generated.
>
> Huh, I cross compiled this on a bunch of ppc configs, but maybe not emough.
>
> No, on the branch I submitted that did not exist.
>
> Probably due to the rebase.
Ehm, no, Andrew, could it be that you accidentally dropped the ppc patch
from mm-new. I can spot all but that patch in there:
https://lkml.kernel.org/r/20250811112631.759341-7-david@redhat.com
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-08-12 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 19:18 kernel test robot
2025-08-12 20:50 ` David Hildenbrand
2025-08-12 20:57 ` David Hildenbrand [this message]
2025-08-12 22:03 ` Andrew Morton
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=522f31cc-f250-4883-8832-0d26ebf5210b@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--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