All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cel@kernel.org
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v1 2/2] libfs: Clean up the simple_offset API
Date: Fri, 12 Apr 2024 13:50:12 +0800	[thread overview]
Message-ID: <202404121313.3QGwuj72-lkp@intel.com> (raw)
In-Reply-To: <20240411182611.203328-3-cel@kernel.org>

Hi,

kernel test robot noticed the following build warnings:

[auto build test WARNING on akpm-mm/mm-everything]
[also build test WARNING on brauner-vfs/vfs.all linus/master v6.9-rc3 next-20240411]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/cel-kernel-org/shmem-Fix-shmem_rename2/20240412-024237
base:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link:    https://lore.kernel.org/r/20240411182611.203328-3-cel%40kernel.org
patch subject: [PATCH v1 2/2] libfs: Clean up the simple_offset API
config: openrisc-allnoconfig (https://download.01.org/0day-ci/archive/20240412/202404121313.3QGwuj72-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240412/202404121313.3QGwuj72-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/202404121313.3QGwuj72-lkp@intel.com/

All warnings (new ones prefixed by >>):

   In file included from include/linux/shmem_fs.h:6,
                    from mm/shmem.c:36:
   include/linux/swap.h:568:6: warning: no previous prototype for 'swap_free_nr' [-Wmissing-prototypes]
     568 | void swap_free_nr(swp_entry_t entry, int nr_pages)
         |      ^~~~~~~~~~~~
>> mm/shmem.c:2483:27: warning: 'shmem_get_offset_ctx' defined but not used [-Wunused-function]
    2483 | static struct offset_ctx *shmem_get_offset_ctx(struct inode *inode)
         |                           ^~~~~~~~~~~~~~~~~~~~


vim +/shmem_get_offset_ctx +2483 mm/shmem.c

e408e695f5f1f6 Theodore Ts'o 2022-07-14  2482  
a2e459555c5f9d Chuck Lever   2023-06-30 @2483  static struct offset_ctx *shmem_get_offset_ctx(struct inode *inode)
a2e459555c5f9d Chuck Lever   2023-06-30  2484  {
a2e459555c5f9d Chuck Lever   2023-06-30  2485  	return &SHMEM_I(inode)->dir_offsets;
a2e459555c5f9d Chuck Lever   2023-06-30  2486  }
a2e459555c5f9d Chuck Lever   2023-06-30  2487  

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

  reply	other threads:[~2024-04-12  5:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11 18:26 [PATCH v1 0/2] Fix shmem_rename2 directory offset calculation cel
2024-04-11 18:26 ` [PATCH v1 1/2] shmem: Fix shmem_rename2() cel
2024-04-11 18:26 ` [PATCH v1 2/2] libfs: Clean up the simple_offset API cel
2024-04-12  5:50   ` kernel test robot [this message]
2024-04-12 14:29 ` [PATCH v1 0/2] Fix shmem_rename2 directory offset calculation Chuck Lever
2024-04-15 14:48   ` Christian Brauner

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=202404121313.3QGwuj72-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cel@kernel.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.