All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [intel-lts:pr/69 1/1] arch/powerpc/lib/sstep.c:245:1: warning: 'inline' is not at beginning of declaration
Date: Mon, 24 Feb 2025 22:24:25 +0800	[thread overview]
Message-ID: <202502242225.SPcLAffN-lkp@intel.com> (raw)

tree:   https://github.com/intel/linux-intel-lts.git pr/69
head:   f36ea6678b4077d9bbb4644e73977fb91d187ab7
commit: e0a0986b446553c6a69fe1bb36250224646b264f [1/1] powerpc: Make load/store emulation use larger memory accesses
config: powerpc-randconfig-001-20250224 (https://download.01.org/0day-ci/archive/20250224/202502242225.SPcLAffN-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250224/202502242225.SPcLAffN-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/202502242225.SPcLAffN-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> arch/powerpc/lib/sstep.c:245:1: warning: 'inline' is not at beginning of declaration [-Wold-style-declaration]
    static int nokprobe_inline copy_mem_in(u8 *dest, unsigned long ea, int nb)
    ^~~~~~
   arch/powerpc/lib/sstep.c:344:1: warning: 'inline' is not at beginning of declaration [-Wold-style-declaration]
    static int nokprobe_inline copy_mem_out(u8 *dest, unsigned long ea, int nb)
    ^~~~~~


vim +/inline +245 arch/powerpc/lib/sstep.c

   240	
   241	/*
   242	 * Copy from userspace to a buffer, using the largest possible
   243	 * aligned accesses, up to sizeof(long).
   244	 */
 > 245	static int nokprobe_inline copy_mem_in(u8 *dest, unsigned long ea, int nb)
   246	{
   247		int err = 0;
   248		int c;
   249	
   250		for (; nb > 0; nb -= c) {
   251			c = max_align(ea);
   252			if (c > nb)
   253				c = max_align(nb);
   254			switch (c) {
   255			case 1:
   256				err = __get_user(*dest, (unsigned char __user *) ea);
   257				break;
   258			case 2:
   259				err = __get_user(*(u16 *)dest,
   260						 (unsigned short __user *) ea);
   261				break;
   262			case 4:
   263				err = __get_user(*(u32 *)dest,
   264						 (unsigned int __user *) ea);
   265				break;
   266	#ifdef __powerpc64__
   267			case 8:
   268				err = __get_user(*(unsigned long *)dest,
   269						 (unsigned long __user *) ea);
   270				break;
   271	#endif
   272			}
   273			if (err)
   274				return err;
   275			dest += c;
   276			ea += c;
   277		}
   278		return 0;
   279	}
   280	

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

                 reply	other threads:[~2025-02-24 14:24 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=202502242225.SPcLAffN-lkp@intel.com \
    --to=lkp@intel.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.