From: kbuild test robot <lkp@intel.com>
To: Radu Pirea <radu.pirea@microchip.com>
Cc: kbuild-all@01.org, richard.genoud@gmail.com,
pirea.radu@gmail.com, lee.jones@linaro.org, robh+dt@kernel.org,
mark.rutland@arm.com, nicolas.ferre@microchip.com,
alexandre.belloni@bootlin.com, gregkh@linuxfoundation.org,
jslaby@suse.com, broonie@kernel.org, linux-spi@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-serial@vger.kernel.org,
Radu Pirea <radu.pirea@microchip.com>
Subject: Re: [RESEND PATCH v11 5/6] spi: at91-usart: add driver for at91-usart as spi
Date: Sun, 2 Sep 2018 05:23:40 +0800 [thread overview]
Message-ID: <201809020500.AUGWBTuR%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180831134141.9335-6-radu.pirea@microchip.com>
Hi Radu,
I love your patch! Perhaps something to improve:
[auto build test WARNING on ljones-mfd/for-mfd-next]
[also build test WARNING on v4.19-rc1 next-20180831]
[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/Radu-Pirea/Driver-for-at91-usart-in-spi-mode/20180901-165150
base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> drivers/spi/spi-at91-usart.c:218:5: sparse: symbol 'at91_usart_spi_transfer_one' was not declared. Should it be static?
>> drivers/spi/spi-at91-usart.c:245:5: sparse: symbol 'at91_usart_spi_prepare_message' was not declared. Should it be static?
>> drivers/spi/spi-at91-usart.c:259:5: sparse: symbol 'at91_usart_spi_unprepare_message' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2018-09-01 21:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 13:41 [RESEND PATCH v11 0/6] Driver for at91 usart in spi mode Radu Pirea
2018-08-31 13:41 ` [RESEND PATCH v11 1/6] MAINTAINERS: add at91 usart mfd driver Radu Pirea
2018-08-31 13:41 ` [RESEND PATCH v11 2/6] dt-bindings: add binding for atmel-usart in SPI mode Radu Pirea
2018-08-31 13:41 ` [RESEND PATCH v11 3/6] mfd: at91-usart: added mfd driver for usart Radu Pirea
2018-08-31 13:41 ` [RESEND PATCH v11 4/6] MAINTAINERS: add at91 usart spi driver Radu Pirea
2018-08-31 13:41 ` [RESEND PATCH v11 5/6] spi: at91-usart: add driver for at91-usart as spi Radu Pirea
2018-09-01 21:23 ` kbuild test robot [this message]
2018-09-01 21:23 ` [RFC PATCH] spi: at91-usart: at91_usart_spi_transfer_one() can be static kbuild test robot
2018-08-31 13:41 ` [RESEND PATCH v11 6/6] tty/serial: atmel: change the driver to work under at91-usart mfd Radu Pirea
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=201809020500.AUGWBTuR%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=kbuild-all@01.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nicolas.ferre@microchip.com \
--cc=pirea.radu@gmail.com \
--cc=radu.pirea@microchip.com \
--cc=richard.genoud@gmail.com \
--cc=robh+dt@kernel.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