From: Mark Brown <broonie@kernel.org>
To: 郭力豪 <lhjeff911@gmail.com>
Cc: sfr@canb.auug.org.au, linux-spi@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
呂芳騰LuWells <wells.lu@sunplus.com>, "lh.kuo" <lh.kuo@sunplus.com>
Subject: Re: [PATCH -next] spi: Fix compiler warning for kernel test
Date: Fri, 28 Jan 2022 19:11:17 +0000 [thread overview]
Message-ID: <YfQ/1aJzebxw2GS+@sirena.org.uk> (raw)
In-Reply-To: <CAGcXWkzM6wbhNFLbYoijq7iS_76nYVod1ySFEDu-BRgnBokEQA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 719 bytes --]
On Fri, Jan 28, 2022 at 10:47:41PM +0800, 郭力豪 wrote:
> Fix compiler warming for kernel test
>
> Fixes: f62ca4e2a863 ("spi: Add spi driver for Sunplus SP7021")
> Signed-off-by: Li-hao Kuo <lhjeff911@gmail.com>
Thanks for adding the signoff but this and the other two patches you
just sent are breaking the tooling - they're sent with HMTL and it looks
like the text parts have been corrupted with at least word wrapping:
> -int sp7021_spi_slave_tx(struct spi_device *spi, struct spi_transfer *xfer)
> +static int sp7021_spi_slave_tx(struct spi_device *spi, struct spi_transfer
> *xfer)
so the diff doesn't work as-is. Can you check and resend please, your
normal posting mechanism works fine?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-01-28 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 2:21 Li-hao Kuo
2022-01-28 12:57 ` Mark Brown
[not found] ` <CAGcXWkzM6wbhNFLbYoijq7iS_76nYVod1ySFEDu-BRgnBokEQA@mail.gmail.com>
2022-01-28 19:11 ` Mark Brown [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=YfQ/1aJzebxw2GS+@sirena.org.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lh.kuo@sunplus.com \
--cc=lhjeff911@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=wells.lu@sunplus.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
all inboxes | Powered by JetHome®