From: kbuild test robot <lkp@intel.com>
To: Shreeya Patel <shreeya.patel23498@gmail.com>
Cc: kbuild-all@01.org, lars@metafoo.de, Michael.Hennerich@analog.com,
jic23@kernel.org, knaack.h@gmx.de, pmeerw@pmeerw.net,
gregkh@linuxfoundation.org, linux-iio@vger.kernel.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Shreeya Patel <shreeya.patel23498@gmail.com>
Subject: [RFC PATCH] Staging: iio: ade7758: __ade7758_spi_write_reg_8() can be static
Date: Thu, 25 Jan 2018 02:53:42 +0800 [thread overview]
Message-ID: <20180124185342.GA40461@xian> (raw)
In-Reply-To: <1516654973-6434-1-git-send-email-shreeya.patel23498@gmail.com>
Fixes: c1960999e575 ("Staging: iio: ade7758: Expand buf_lock to cover both buffer")
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
ade7758_core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/iio/meter/ade7758_core.c b/drivers/staging/iio/meter/ade7758_core.c
index 7f8f8c4..5794ebb 100644
--- a/drivers/staging/iio/meter/ade7758_core.c
+++ b/drivers/staging/iio/meter/ade7758_core.c
@@ -25,7 +25,7 @@
#include "ade7758.h"
/* Unlocked version of ade7758_spi_write_reg_8 function */
-int __ade7758_spi_write_reg_8(struct device *dev, u8 reg_address, u8 val)
+static int __ade7758_spi_write_reg_8(struct device *dev, u8 reg_address, u8 val)
{
struct iio_dev *indio_dev = dev_to_iio_dev(dev);
struct ade7758_state *st = iio_priv(indio_dev);
@@ -101,7 +101,7 @@ static int ade7758_spi_write_reg_24(struct device *dev, u8 reg_address,
}
/* Unlocked version of ade7758_spi_read_reg_16 function */
-int __ade7758_spi_read_reg_8(struct device *dev, u8 reg_address, u8 *val)
+static int __ade7758_spi_read_reg_8(struct device *dev, u8 reg_address, u8 *val)
{
struct iio_dev *indio_dev = dev_to_iio_dev(dev);
struct ade7758_state *st = iio_priv(indio_dev);
next prev parent reply other threads:[~2018-01-24 18:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 21:02 [PATCH] Staging: iio: ade7758: Expand buf_lock to cover both buffer Shreeya Patel
2018-01-23 11:40 ` Ardelean, Alexandru
2018-01-23 12:00 ` Jonathan Cameron
2018-01-24 15:01 ` Shreeya Patel
2018-01-24 18:53 ` kbuild test robot [this message]
2018-01-24 18:53 ` 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=20180124185342.GA40461@xian \
--to=lkp@intel.com \
--cc=Michael.Hennerich@analog.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=kbuild-all@01.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=shreeya.patel23498@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;
as well as URLs for NNTP newsgroup(s).