From: kernel test robot <lkp@intel.com>
To: Jorgen Hansen <jhansen@vmware.com>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Cc: kbuild-all@lists.01.org, gregkh@linuxfoundation.org,
pv-drivers@vmware.com, Jorgen Hansen <jhansen@vmware.com>,
Vishnu Dasa <vdasa@vmware.com>
Subject: [RFC PATCH] VMCI: dma dg: vmci_read_reg() can be static
Date: Thu, 3 Feb 2022 05:09:43 +0800 [thread overview]
Message-ID: <20220202210943.GA88437@f185d0c9484e> (raw)
In-Reply-To: <20220202144910.10349-3-jhansen@vmware.com>
drivers/misc/vmw_vmci/vmci_guest.c:93:14: warning: symbol 'vmci_read_reg' was not declared. Should it be static?
drivers/misc/vmw_vmci/vmci_guest.c:100:6: warning: symbol 'vmci_write_reg' was not declared. Should it be static?
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
vmci_guest.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/misc/vmw_vmci/vmci_guest.c b/drivers/misc/vmw_vmci/vmci_guest.c
index d00430e5aba36..081f7b0c23f5f 100644
--- a/drivers/misc/vmw_vmci/vmci_guest.c
+++ b/drivers/misc/vmw_vmci/vmci_guest.c
@@ -90,14 +90,14 @@ u32 vmci_get_vm_context_id(void)
return vm_context_id;
}
-unsigned int vmci_read_reg(struct vmci_guest_device *dev, u32 reg)
+static unsigned int vmci_read_reg(struct vmci_guest_device *dev, u32 reg)
{
if (dev->mmio_base != NULL)
return readl(dev->mmio_base + reg);
return ioread32(dev->iobase + reg);
}
-void vmci_write_reg(struct vmci_guest_device *dev, u32 val, u32 reg)
+static void vmci_write_reg(struct vmci_guest_device *dev, u32 val, u32 reg)
{
if (dev->mmio_base != NULL)
writel(val, dev->mmio_base + reg);
next prev parent reply other threads:[~2022-02-02 21:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 14:49 [PATCH 0/8] VMCI: dma dg: Add support for DMA datagrams Jorgen Hansen
2022-02-02 14:49 ` [PATCH 1/8] VMCI: dma dg: whitespace formatting change for vmci register defines Jorgen Hansen
2022-02-02 14:49 ` [PATCH 2/8] VMCI: dma dg: add MMIO access to registers Jorgen Hansen
2022-02-02 16:23 ` kernel test robot
2022-02-02 21:09 ` kernel test robot [this message]
2022-02-02 21:18 ` kernel test robot
2022-02-02 22:19 ` kernel test robot
2022-02-02 14:49 ` [PATCH 3/8] VMCI: dma dg: detect DMA datagram capability Jorgen Hansen
2022-02-02 14:49 ` [PATCH 4/8] VMCI: dma dg: set OS page size Jorgen Hansen
2022-02-02 14:49 ` [PATCH 5/8] VMCI: dma dg: register dummy IRQ handlers for DMA datagrams Jorgen Hansen
2022-02-02 14:49 ` [PATCH 6/8] VMCI: dma dg: allocate send and receive buffers " Jorgen Hansen
2022-02-03 0:18 ` kernel test robot
2022-02-02 14:49 ` [PATCH 7/8] VMCI: dma dg: add support for DMA datagrams sends Jorgen Hansen
2022-02-02 17:14 ` kernel test robot
2022-02-03 0:48 ` kernel test robot
2022-02-03 2:31 ` [RFC PATCH] VMCI: dma dg: vmci_write_data() can be static kernel test robot
2022-02-03 2:39 ` [PATCH 7/8] VMCI: dma dg: add support for DMA datagrams sends kernel test robot
2022-02-02 14:49 ` [PATCH 8/8] VMCI: dma dg: add support for DMA datagrams receive Jorgen Hansen
2022-07-29 22:07 ` Nathan Chancellor
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=20220202210943.GA88437@f185d0c9484e \
--to=lkp@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jhansen@vmware.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pv-drivers@vmware.com \
--cc=vdasa@vmware.com \
--cc=virtualization@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox