All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: oe-kbuild-all@lists.linux.dev, Janne Grunau <j@jannau.net>
Subject: [asahilinux:bits/050-nvme 2/4] drivers/nvme/host/apple.c:208:14: sparse: sparse: symbol 'flush_interval' was not declared. Should it be static?
Date: Mon, 10 Feb 2025 20:11:08 +0800	[thread overview]
Message-ID: <202502101947.VSemm0S7-lkp@intel.com> (raw)

tree:   https://github.com/AsahiLinux/linux bits/050-nvme
head:   64364dddbb6079a18e8119f64748a217b51d7e65
commit: cefae9739746756817c42688662ffb8e5ac846ca [2/4] apple-nvme: defer cache flushes by a specified amount
config: arm64-randconfig-r112-20250210 (https://download.01.org/0day-ci/archive/20250210/202502101947.VSemm0S7-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce: (https://download.01.org/0day-ci/archive/20250210/202502101947.VSemm0S7-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/202502101947.VSemm0S7-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/nvme/host/apple.c:208:14: sparse: sparse: symbol 'flush_interval' was not declared. Should it be static?

vim +/flush_interval +208 drivers/nvme/host/apple.c

   207	
 > 208	unsigned int flush_interval = 1000;
   209	module_param(flush_interval, uint, 0644);
   210	MODULE_PARM_DESC(flush_interval, "Grace period in msecs between flushes");
   211	

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

                 reply	other threads:[~2025-02-10 12:11 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=202502101947.VSemm0S7-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=axboe@kernel.dk \
    --cc=j@jannau.net \
    --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.