From: kernel test robot <lkp@intel.com>
To: Riyan Dhiman <riyandhiman14@gmail.com>, gregkh@linuxfoundation.org
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev,
Riyan Dhiman <riyandhiman14@gmail.com>
Subject: Re: [PATCH] staging: vme_user: Added static to image_desc and vme_user_vma_priv struct
Date: Tue, 27 Aug 2024 06:38:24 +0800 [thread overview]
Message-ID: <202408270655.m9x8rJA5-lkp@intel.com> (raw)
In-Reply-To: <20240825035514.40095-1-riyandhiman14@gmail.com>
Hi Riyan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on staging/staging-testing]
url: https://github.com/intel-lab-lkp/linux/commits/Riyan-Dhiman/staging-vme_user-Added-static-to-image_desc-and-vme_user_vma_priv-struct/20240826-142747
base: staging/staging-testing
patch link: https://lore.kernel.org/r/20240825035514.40095-1-riyandhiman14%40gmail.com
patch subject: [PATCH] staging: vme_user: Added static to image_desc and vme_user_vma_priv struct
config: arc-allyesconfig (https://download.01.org/0day-ci/archive/20240827/202408270655.m9x8rJA5-lkp@intel.com/config)
compiler: arceb-elf-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240827/202408270655.m9x8rJA5-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/202408270655.m9x8rJA5-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/staging/vme_user/vme_user.c:99:1: warning: useless storage class specifier in empty declaration
99 | };
| ^
drivers/staging/vme_user/vme_user.c:120:1: warning: useless storage class specifier in empty declaration
120 | };
| ^
vim +99 drivers/staging/vme_user/vme_user.c
f00a86d98a1ec3 drivers/staging/vme/devices/vme_user.c Martyn Welch 2009-07-31 87
f00a86d98a1ec3 drivers/staging/vme/devices/vme_user.c Martyn Welch 2009-07-31 88 /*
f00a86d98a1ec3 drivers/staging/vme/devices/vme_user.c Martyn Welch 2009-07-31 89 * Structure to handle image related parameters.
f00a86d98a1ec3 drivers/staging/vme/devices/vme_user.c Martyn Welch 2009-07-31 90 */
e2d30086b6cc13 drivers/staging/vme_user/vme_user.c Riyan Dhiman 2024-08-25 91 static struct image_desc {
0a81a0f768e5bb drivers/staging/vme/devices/vme_user.c Emilio G. Cota 2010-11-12 92 void *kern_buf; /* Buffer address in kernel space */
f00a86d98a1ec3 drivers/staging/vme/devices/vme_user.c Martyn Welch 2009-07-31 93 dma_addr_t pci_buf; /* Buffer address in PCI address space */
f00a86d98a1ec3 drivers/staging/vme/devices/vme_user.c Martyn Welch 2009-07-31 94 unsigned long long size_buf; /* Buffer size */
ecb3b80ff968f1 drivers/staging/vme/devices/vme_user.c Santosh Nayak 2012-04-03 95 struct mutex mutex; /* Mutex for locking image */
f00a86d98a1ec3 drivers/staging/vme/devices/vme_user.c Martyn Welch 2009-07-31 96 struct device *device; /* Sysfs device */
f00a86d98a1ec3 drivers/staging/vme/devices/vme_user.c Martyn Welch 2009-07-31 97 struct vme_resource *resource; /* VME resource */
c74a804f115bde drivers/staging/vme/devices/vme_user.c Dmitry Kalinkin 2015-02-26 98 int mmap_count; /* Number of current mmap's */
584721cab2bdd2 drivers/staging/vme/devices/vme_user.c Vincent Bossier 2011-06-03 @99 };
cd974d35ab784d drivers/staging/vme/devices/vme_user.c Dmitry Kalinkin 2015-06-26 100
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-08-26 22:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-25 3:55 [PATCH] staging: vme_user: Added static to image_desc and vme_user_vma_priv struct Riyan Dhiman
2024-08-25 8:13 ` Nam Cao
2024-08-26 22:17 ` kernel test robot
2024-08-26 22:38 ` kernel test robot [this message]
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=202408270655.m9x8rJA5-lkp@intel.com \
--to=lkp@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=riyandhiman14@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox