All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Mike Rapoport (IBM)" <rppt@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, Mike Rapoport <rppt@kernel.org>
Subject: [rppt:jitalloc/v2.2 10/12] arch/powerpc/mm/mem.c:419:18: error: 'struct execmem_range' has no member named 'text'
Date: Wed, 21 Jun 2023 21:41:13 +0800	[thread overview]
Message-ID: <202306212120.m2OLgLBW-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/rppt/linux.git jitalloc/v2.2
head:   4d3b7e33eca22e1fe243f586c13c875d248d29f6
commit: 5f24f0d18c8afbea8c6adc7274c588f256197685 [10/12] arch: make execmem setup available regardless of CONFIG_MODULES
config: powerpc-allmodconfig (https://download.01.org/0day-ci/archive/20230621/202306212120.m2OLgLBW-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230621/202306212120.m2OLgLBW-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/202306212120.m2OLgLBW-lkp@intel.com/

All errors (new ones prefixed by >>):

>> arch/powerpc/mm/mem.c:419:18: error: 'struct execmem_range' has no member named 'text'
     419 |                 .text = {
         |                  ^~~~
   arch/powerpc/mm/mem.c:419:17: warning: braces around scalar initializer
     419 |                 .text = {
         |                 ^
   arch/powerpc/mm/mem.c:419:17: note: (near initialization for 'execmem_params.jit.start')
>> arch/powerpc/mm/mem.c:420:25: error: field name not in record or union initializer
     420 |                         .alignment = 1,
         |                         ^
   arch/powerpc/mm/mem.c:420:25: note: (near initialization for 'execmem_params.jit.start')
   arch/powerpc/mm/mem.c: In function 'execmem_arch_params':
   arch/powerpc/mm/mem.c:457:27: error: 'struct execmem_range' has no member named 'text'
     457 |         execmem_params.jit.text.start = VMALLOC_START;
         |                           ^
   arch/powerpc/mm/mem.c:458:27: error: 'struct execmem_range' has no member named 'text'
     458 |         execmem_params.jit.text.end = VMALLOC_END;
         |                           ^
   arch/powerpc/mm/mem.c:461:35: error: 'struct execmem_range' has no member named 'text'
     461 |                 execmem_params.jit.text.pgprot = PAGE_KERNEL_ROX;
         |                                   ^
   arch/powerpc/mm/mem.c:463:35: error: 'struct execmem_range' has no member named 'text'
     463 |                 execmem_params.jit.text.pgprot = PAGE_KERNEL_EXEC;
         |                                   ^


vim +419 arch/powerpc/mm/mem.c

   410	
   411	#ifdef CONFIG_EXECMEM
   412	static struct execmem_params execmem_params __ro_after_init = {
   413		.modules = {
   414			.text = {
   415				.alignment = 1,
   416			},
   417		},
   418		.jit = {
 > 419			.text = {
 > 420				.alignment = 1,
   421			},
   422		},
   423	};
   424	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2023-06-21 13:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202306212120.m2OLgLBW-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rppt@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.