From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [superna9999:amlogic/v5.7/khadas-mcu 4/4] drivers/nvmem/khadas-mcu-user-mem.c:42:15: warning: Unused variable: size [unusedVariable]
Date: Tue, 07 Apr 2020 16:37:23 +0800 [thread overview]
Message-ID: <20200407083723.GC8179@shao2-debian> (raw)
[-- Attachment #1: Type: text/plain, Size: 3140 bytes --]
tree: https://github.com/superna9999/linux amlogic/v5.7/khadas-mcu
head: 9109063d9d3d5c699b22293d5099eabb83e0adbc
commit: 9109063d9d3d5c699b22293d5099eabb83e0adbc [4/4] nvmem: add support for the Khadas MCU Programmable User Memory
:::::: branch date: 7 hours ago
:::::: commit date: 7 hours ago
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
cppcheck warnings: (new ones prefixed by >>)
>> drivers/nvmem/khadas-mcu-user-mem.c:42:15: warning: Unused variable: size [unusedVariable]
unsigned int size;
^
>> drivers/nvmem/khadas-mcu-user-mem.c:43:6: warning: Unused variable: ret [unusedVariable]
int ret;
^
# https://github.com/superna9999/linux/commit/9109063d9d3d5c699b22293d5099eabb83e0adbc
git remote add superna9999 https://github.com/superna9999/linux
git remote update superna9999
git checkout 9109063d9d3d5c699b22293d5099eabb83e0adbc
vim +42 drivers/nvmem/khadas-mcu-user-mem.c
9109063d9d3d5c Neil Armstrong 2020-04-05 35
9109063d9d3d5c Neil Armstrong 2020-04-05 36 static int khadas_mcu_user_mem_probe(struct platform_device *pdev)
9109063d9d3d5c Neil Armstrong 2020-04-05 37 {
9109063d9d3d5c Neil Armstrong 2020-04-05 38 struct khadas_mcu *khadas_mcu = dev_get_drvdata(pdev->dev.parent);
9109063d9d3d5c Neil Armstrong 2020-04-05 39 struct device *dev = &pdev->dev;
9109063d9d3d5c Neil Armstrong 2020-04-05 40 struct nvmem_device *nvmem;
9109063d9d3d5c Neil Armstrong 2020-04-05 41 struct nvmem_config *econfig;
9109063d9d3d5c Neil Armstrong 2020-04-05 @42 unsigned int size;
9109063d9d3d5c Neil Armstrong 2020-04-05 @43 int ret;
9109063d9d3d5c Neil Armstrong 2020-04-05 44
9109063d9d3d5c Neil Armstrong 2020-04-05 45 econfig = devm_kzalloc(dev, sizeof(*econfig), GFP_KERNEL);
9109063d9d3d5c Neil Armstrong 2020-04-05 46 if (!econfig)
9109063d9d3d5c Neil Armstrong 2020-04-05 47 return -ENOMEM;
9109063d9d3d5c Neil Armstrong 2020-04-05 48
9109063d9d3d5c Neil Armstrong 2020-04-05 49 econfig->dev = dev;
9109063d9d3d5c Neil Armstrong 2020-04-05 50 econfig->name = dev_name(dev);
9109063d9d3d5c Neil Armstrong 2020-04-05 51 econfig->stride = 1;
9109063d9d3d5c Neil Armstrong 2020-04-05 52 econfig->word_size = 1;
9109063d9d3d5c Neil Armstrong 2020-04-05 53 econfig->reg_read = khadas_mcu_user_mem_read;
9109063d9d3d5c Neil Armstrong 2020-04-05 54 econfig->reg_write = khadas_mcu_user_mem_write;
9109063d9d3d5c Neil Armstrong 2020-04-05 55 econfig->size = 56;
9109063d9d3d5c Neil Armstrong 2020-04-05 56 econfig->priv = khadas_mcu;
9109063d9d3d5c Neil Armstrong 2020-04-05 57
9109063d9d3d5c Neil Armstrong 2020-04-05 58 nvmem = devm_nvmem_register(&pdev->dev, econfig);
9109063d9d3d5c Neil Armstrong 2020-04-05 59
9109063d9d3d5c Neil Armstrong 2020-04-05 60 return PTR_ERR_OR_ZERO(nvmem);
9109063d9d3d5c Neil Armstrong 2020-04-05 61 }
9109063d9d3d5c Neil Armstrong 2020-04-05 62
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
reply other threads:[~2020-04-07 8:37 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=20200407083723.GC8179@shao2-debian \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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.