public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Amit, Kumar, Mahapatra," <amit.kumar-mahapatra@xilinx.com>
Cc: Naga Sureshkumar Relli <naga.sureshkumar.relli@xilinx.com>,
	Michal Simek <monstr@monstr.eu>,
	kbuild-all@lists.01.org, Harini Katakam <harinik@xilinx.com>,
	Soren Brinkmann <soren.brinkmann@xilinx.com>,
	Punnaiah Choudary Kalluri <punnaia@xilinx.com>,
	linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH xlnx] spi: update_stripe() can be static
Date: Thu, 4 Jun 2020 06:27:48 +0800	[thread overview]
Message-ID: <20200603222748.GA157363@8aa1beddc6c9> (raw)
In-Reply-To: <202006040620.KNC6r6Nv%lkp@intel.com>


Fixes: 6cac93c63316 ("spi: Add Zynq QSPI controller driver")
Signed-off-by: kernel test robot <lkp@intel.com>
---
 spi-mem.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/spi/spi-mem.c b/drivers/spi/spi-mem.c
index d4e807c8263a4..b95a7fd0bee2d 100644
--- a/drivers/spi/spi-mem.c
+++ b/drivers/spi/spi-mem.c
@@ -15,7 +15,7 @@
 
 #define SPI_MEM_MAX_BUSWIDTH		8
 
-bool update_stripe(const u8 opcode)
+static bool update_stripe(const u8 opcode)
 {
 	if (opcode ==  SPINOR_OP_BE_4K ||
 	    opcode ==  SPINOR_OP_BE_32K ||

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2020-06-03 22:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 22:27 [xlnx:master 9537/10031] drivers/spi/spi-mem.c:18:6: sparse: sparse: symbol 'update_stripe' was not declared. Should it be kernel test robot
2020-06-03 22:27 ` kernel test robot [this message]

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=20200603222748.GA157363@8aa1beddc6c9 \
    --to=lkp@intel.com \
    --cc=amit.kumar-mahapatra@xilinx.com \
    --cc=harinik@xilinx.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=monstr@monstr.eu \
    --cc=naga.sureshkumar.relli@xilinx.com \
    --cc=punnaia@xilinx.com \
    --cc=soren.brinkmann@xilinx.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