All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android14-5.15 1/5] mm/pgsize_migration.c:98: warning: expecting prototype for What(). Prototype was for init_pgsize_migration() instead
Date: Tue, 16 Apr 2024 07:44:56 +0800	[thread overview]
Message-ID: <202404160720.XSWZtpfE-lkp@intel.com> (raw)

tree:   https://android.googlesource.com/kernel/common android14-5.15
head:   084d22016ccabe60338ea69b0a1c4c264551bd4c
commit: 9274c308d8469e26a5f3fb8b598000edcff6b135 [1/5] ANDROID: 16K: Introduce /sys/kernel/mm/pgsize_miration/enabled
config: arm-allnoconfig (https://download.01.org/0day-ci/archive/20240416/202404160720.XSWZtpfE-lkp@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project 7089c359a3845323f6f30c44a47dd901f2edfe63)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240416/202404160720.XSWZtpfE-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/202404160720.XSWZtpfE-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> mm/pgsize_migration.c:98: warning: expecting prototype for What(). Prototype was for init_pgsize_migration() instead


vim +98 mm/pgsize_migration.c

    81	
    82	/**
    83	 * What:          /sys/kernel/mm/pgsize_migration/enabled
    84	 * Date:          April 2024
    85	 * KernelVersion: v5.4+ (GKI kernels)
    86	 * Contact:       Kalesh Singh <kaleshsingh@google.com>
    87	 * Description:   /sys/kernel/mm/pgsize_migration/enabled
    88	 *                allows for userspace to turn on or off page size
    89	 *                migration mitigations necessary for app compatibility
    90	 *                during Android's transition from 4kB to 16kB page size.
    91	 *                Such mitigations include preserving /proc/<pid>/[s]maps
    92	 *                output as if there was no segment extension by the
    93	 *                dynamic loader; and preventing fault around in the padding
    94	 *                sections of ELF LOAD segment mappings.
    95	 * Users:         Bionic's dynamic linker
    96	 */
    97	static int __init init_pgsize_migration(void)
  > 98	{

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

                 reply	other threads:[~2024-04-15 23:45 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=202404160720.XSWZtpfE-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cros-kernel-buildreports@googlegroups.com \
    --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 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.