From: kernel test robot <lkp@intel.com>
To: James Smart <james.smart@broadcom.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Dick Kennedy <dick.kennedy@broadcom.com>
Subject: [linux-next:master 1211/7024] drivers/scsi/lpfc/lpfc_ct.c:3015:1: warning: no previous prototype for 'lpfc_fdmi_vendor_attr_mi'
Date: Thu, 19 Nov 2020 23:18:46 +0800 [thread overview]
Message-ID: <202011192342.mpf4QH5p-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2157 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: f8550c0d35df3d027724b250a8c5888dfb2fa749
commit: 8aaa7bcf07a2eea5ffb6d4ee776379c0e0154f6d [1211/7024] scsi: lpfc: Add FDMI Vendor MIB support
config: i386-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=8aaa7bcf07a2eea5ffb6d4ee776379c0e0154f6d
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 8aaa7bcf07a2eea5ffb6d4ee776379c0e0154f6d
# save the attached .config to linux build tree
make W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/scsi/lpfc/lpfc_ct.c:3015:1: warning: no previous prototype for 'lpfc_fdmi_vendor_attr_mi' [-Wmissing-prototypes]
3015 | lpfc_fdmi_vendor_attr_mi(struct lpfc_vport *vport,
| ^~~~~~~~~~~~~~~~~~~~~~~~
vim +/lpfc_fdmi_vendor_attr_mi +3015 drivers/scsi/lpfc/lpfc_ct.c
3013
3014 int
> 3015 lpfc_fdmi_vendor_attr_mi(struct lpfc_vport *vport,
3016 struct lpfc_fdmi_attr_def *ad)
3017 {
3018 struct lpfc_hba *phba = vport->phba;
3019 struct lpfc_fdmi_attr_entry *ae;
3020 uint32_t len, size;
3021 char mibrevision[16];
3022
3023 ae = (struct lpfc_fdmi_attr_entry *)&ad->AttrValue;
3024 memset(ae, 0, 256);
3025 sprintf(mibrevision, "ELXE2EM:%04d",
3026 phba->sli4_hba.pc_sli4_params.mi_value);
3027 strncpy(ae->un.AttrString, &mibrevision[0], sizeof(ae->un.AttrString));
3028 len = strnlen(ae->un.AttrString, sizeof(ae->un.AttrString));
3029 len += (len & 3) ? (4 - (len & 3)) : 4;
3030 size = FOURBYTES + len;
3031 ad->AttrLen = cpu_to_be16(size);
3032 ad->AttrType = cpu_to_be16(RPRT_VENDOR_MI);
3033 return size;
3034 }
3035
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 75986 bytes --]
reply other threads:[~2020-11-19 15:19 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=202011192342.mpf4QH5p-lkp@intel.com \
--to=lkp@intel.com \
--cc=dick.kennedy@broadcom.com \
--cc=james.smart@broadcom.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=martin.petersen@oracle.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