From: Scott Wood <scottwood@freescale.com>
To: Zhao Qiang <B45475@freescale.com>
Cc: B07421@freescale.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] spi: include "int ret" with macro
Date: Tue, 24 Jun 2014 13:55:01 -0500 [thread overview]
Message-ID: <1403636101.26908.26.camel@snotra.buserror.net> (raw)
In-Reply-To: <1403596509-12411-1-git-send-email-B45475@freescale.com>
On Tue, 2014-06-24 at 15:55 +0800, Zhao Qiang wrote:
> ret is unused when CONFIG_FSL_SOC defined,
> so include it with "#ifndef CONFIG_FSL_SOC".
>
> Signed-off-by: Zhao Qiang <B45475@freescale.com>
> ---
> drivers/spi/spi-fsl-lib.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
This needs to be sent to the SPI list and maintainer.
-Scott
next prev parent reply other threads:[~2014-06-24 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 7:55 [PATCH] spi: include "int ret" with macro Zhao Qiang
2014-06-24 18:55 ` Scott Wood [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-25 1:54 Zhao Qiang
2014-06-25 8:44 ` David Laight
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=1403636101.26908.26.camel@snotra.buserror.net \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=B45475@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).