From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, fanyizhen1995 <en_0015767@163.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:OLK-5.10 2516/2516] drivers/ub/urma/ubcore/ubcore_umem.c:227:21: warning: no previous prototype for 'ubcore_umem_get'
Date: Tue, 3 Dec 2024 04:34:34 +0800 [thread overview]
Message-ID: <202412030455.2cb7zJmc-lkp@intel.com> (raw)
Hi Yizhen,
FYI, the error/warning still remains.
tree: https://gitee.com/openeuler/kernel.git OLK-5.10
head: 929a9df37c1b7dec73fd417d79a116d02a8f9380
commit: f6206cf05e28a7f455850a4e2de8162890f50073 [2516/2516] ub: add memory map api in ubcore
config: arm64-randconfig-003-20241203 (https://download.01.org/0day-ci/archive/20241203/202412030455.2cb7zJmc-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241203/202412030455.2cb7zJmc-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/202412030455.2cb7zJmc-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/ub/urma/ubcore/ubcore_umem.c:227:21: warning: no previous prototype for 'ubcore_umem_get' [-Wmissing-prototypes]
227 | struct ubcore_umem *ubcore_umem_get(struct ubcore_device *dev, uint64_t va, uint64_t len,
| ^~~~~~~~~~~~~~~
>> drivers/ub/urma/ubcore/ubcore_umem.c:245:6: warning: no previous prototype for 'ubcore_umem_release' [-Wmissing-prototypes]
245 | void ubcore_umem_release(struct ubcore_umem *umem)
| ^~~~~~~~~~~~~~~~~~~
vim +/ubcore_umem_get +227 drivers/ub/urma/ubcore/ubcore_umem.c
226
> 227 struct ubcore_umem *ubcore_umem_get(struct ubcore_device *dev, uint64_t va, uint64_t len,
228 union ubcore_umem_flag flag)
229 {
230 struct page **page_list;
231 int ret;
232
233 ret = umem_verify_input(dev, va, len, flag);
234 if (ret < 0)
235 return ERR_PTR(ret);
236
237 page_list = (struct page **)__get_free_page(GFP_KERNEL);
238 if (page_list == 0)
239 return ERR_PTR(-ENOMEM);
240
241 return ubcore_get_target_umem(dev, va, len, flag, page_list);
242 }
243 EXPORT_SYMBOL(ubcore_umem_get);
244
> 245 void ubcore_umem_release(struct ubcore_umem *umem)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-12-02 20:36 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=202412030455.2cb7zJmc-lkp@intel.com \
--to=lkp@intel.com \
--cc=en_0015767@163.com \
--cc=kernel@openeuler.org \
--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.