From: lkp@intel.com (kbuild test robot)
Subject: [PATCH 3/6] mpt3sas: Introduce API's to get BAR0 mapped buffer address.
Date: Sun, 21 Jan 2018 01:24:41 +0800 [thread overview]
Message-ID: <201801210120.wtT4VJUt%fengguang.wu@intel.com> (raw)
In-Reply-To: <1516365462-14708-4-git-send-email-suganath-prabu.subramani@broadcom.com>
Hi Suganath,
I love your patch! Perhaps something to improve:
[auto build test WARNING on scsi/for-next]
[also build test WARNING on v4.15-rc8 next-20180119]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Suganath-Prabu-S/mpt3sas-Add-PCI-device-ID-for-Andromeda/20180121-002454
base: https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git for-next
config: i386-randconfig-x017-201803 (attached as .config)
compiler: gcc-7 (Debian 7.2.0-12) 7.2.1 20171025
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed by >>):
drivers/scsi/mpt3sas/mpt3sas_base.c: In function '_base_get_chain_phys':
>> drivers/scsi/mpt3sas/mpt3sas_base.c:171:21: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
base_chain_phys = (void *)ioc->chip_phys + MPI_FRAME_START_OFFSET +
^
At top level:
drivers/scsi/mpt3sas/mpt3sas_base.c:212:1: warning: '_base_get_buffer_phys_bar0' defined but not used [-Wunused-function]
_base_get_buffer_phys_bar0(struct MPT3SAS_ADAPTER *ioc, u16 smid)
^~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/scsi/mpt3sas/mpt3sas_base.c:191:1: warning: '_base_get_buffer_bar0' defined but not used [-Wunused-function]
_base_get_buffer_bar0(struct MPT3SAS_ADAPTER *ioc, u16 smid)
^~~~~~~~~~~~~~~~~~~~~
vim +171 drivers/scsi/mpt3sas/mpt3sas_base.c
152
153 /**
154 * _base_get_chain_phys - Calculates and Returns physical address
155 * in BAR0 for scatter gather chains, for
156 * the provided smid.
157 *
158 * @ioc: per adapter object
159 * @smid: system request message index
160 * @sge_chain_count: Scatter gather chain count.
161 *
162 * @Return - Physical chain address.
163 */
164 static inline void *
165 _base_get_chain_phys(struct MPT3SAS_ADAPTER *ioc, u16 smid,
166 u8 sge_chain_count)
167 {
168 void *base_chain_phys, *chain_phys;
169 u16 cmd_credit = ioc->facts.RequestCredit + 1;
170
> 171 base_chain_phys = (void *)ioc->chip_phys + MPI_FRAME_START_OFFSET +
172 (cmd_credit * ioc->request_sz) +
173 REPLY_FREE_POOL_SIZE;
174 chain_phys = base_chain_phys + (smid * ioc->facts.MaxChainDepth *
175 ioc->request_sz) + (sge_chain_count * ioc->request_sz);
176 return chain_phys;
177 }
178
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.gz
Type: application/gzip
Size: 29932 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-nvme/attachments/20180121/26642ac9/attachment-0001.gz>
next prev parent reply other threads:[~2018-01-20 17:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 12:37 [PATCH 0/6] mpt3sas: Adding MPI Endpoint device support Suganath Prabu S
2018-01-19 12:37 ` [PATCH 1/6] mpt3sas: Add PCI device ID for Andromeda Suganath Prabu S
2018-01-19 12:37 ` [PATCH 2/6] mpt3sas: Configure reply post queue depth, DMA and sgl tablesize Suganath Prabu S
2018-01-19 12:37 ` [PATCH 3/6] mpt3sas: Introduce API's to get BAR0 mapped buffer address Suganath Prabu S
2018-01-20 17:24 ` kbuild test robot [this message]
2018-01-19 12:37 ` [PATCH 4/6] mpt3sas: Introduce Base function for cloning Suganath Prabu S
2018-01-20 17:57 ` kbuild test robot
2018-01-20 18:07 ` kbuild test robot
2018-01-24 5:44 ` Suganath Prabu Subramani
2018-01-19 12:37 ` [PATCH 5/6] mpt3sas: Introduce function to clone mpi request Suganath Prabu S
2018-01-20 18:38 ` kbuild test robot
2018-01-22 14:38 ` Tomas Henzl
2018-02-23 10:15 ` Suganath Prabu Subramani
2018-01-19 12:37 ` [PATCH 6/6] mpt3sas: Introduce function to clone mpi reply Suganath Prabu S
2018-01-20 19:01 ` kbuild test robot
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=201801210120.wtT4VJUt%fengguang.wu@intel.com \
--to=lkp@intel.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