All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, Yang Yingliang <yangyingliang@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:openEuler-1.0-LTS 15243/23920] arch/arm64/kernel/mpam/mpam_device.c:99:24: warning: no previous prototype for 'mpam_component_get'
Date: Thu, 31 Oct 2024 15:05:42 +0800	[thread overview]
Message-ID: <202410311541.Ld1wpJ0T-lkp@intel.com> (raw)

tree:   https://gitee.com/openeuler/kernel.git openEuler-1.0-LTS
head:   c6de47cf1f63ecc3ed337601e06ab8dc1c707563
commit: 73d5cd426ed0b4aed565a11aa8eb86d90b444d94 [15243/23920] arm64/mpam: Add mpam driver discovery phase and kbuild boiler plate
config: arm64-randconfig-001-20241029 (https://download.01.org/0day-ci/archive/20241031/202410311541.Ld1wpJ0T-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241031/202410311541.Ld1wpJ0T-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/202410311541.Ld1wpJ0T-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> arch/arm64/kernel/mpam/mpam_device.c:99:24: warning: no previous prototype for 'mpam_component_get' [-Wmissing-prototypes]
      99 | struct mpam_component *mpam_component_get(struct mpam_class *class, int id,
         |                        ^~~~~~~~~~~~~~~~~~
   arch/arm64/kernel/mpam/mpam_device.c:190:1: warning: no previous prototype for '__mpam_device_create' [-Wmissing-prototypes]
     190 | __mpam_device_create(u8 level_idx, enum mpam_class_types type,
         | ^~~~~~~~~~~~~~~~~~~~
   arch/arm64/kernel/mpam/mpam_device.c:248:12: warning: no previous prototype for 'mpam_discovery_start' [-Wmissing-prototypes]
     248 | int __init mpam_discovery_start(void)
         |            ^~~~~~~~~~~~~~~~~~~~
   arch/arm64/kernel/mpam/mpam_device.c:256:12: warning: no previous prototype for 'mpam_discovery_complete' [-Wmissing-prototypes]
     256 | int __init mpam_discovery_complete(void)
         |            ^~~~~~~~~~~~~~~~~~~~~~~
   arch/arm64/kernel/mpam/mpam_device.c:261:13: warning: no previous prototype for 'mpam_discovery_failed' [-Wmissing-prototypes]
     261 | void __init mpam_discovery_failed(void)
         |             ^~~~~~~~~~~~~~~~~~~~~


vim +/mpam_component_get +99 arch/arm64/kernel/mpam/mpam_device.c

    98	
  > 99	struct mpam_component *mpam_component_get(struct mpam_class *class, int id,
   100							bool alloc)
   101	{
   102		struct mpam_component *comp;
   103	
   104		list_for_each_entry(comp, &class->components, class_list) {
   105			if (comp->comp_id == id)
   106				return comp;
   107		}
   108	
   109		if (!alloc)
   110			return ERR_PTR(-ENOENT);
   111	
   112		comp = mpam_component_alloc(id);
   113		if (IS_ERR(comp))
   114			return comp;
   115	
   116		list_add(&comp->class_list, &class->components);
   117	
   118		return comp;
   119	}
   120	

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

                 reply	other threads:[~2024-10-31  7:06 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=202410311541.Ld1wpJ0T-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kernel@openeuler.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=yangyingliang@huawei.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 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.