From: Randy Dunlap <randy.dunlap@oracle.com>
To: Andres Salomon <dilinger@queued.net>
Cc: David Brownell <dbrownell@users.sourceforge.net>,
Grant Likely <grant.likely@secretlab.ca>,
spi-devel-general@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] spi/spi_altera: fix build error
Date: Tue, 22 Feb 2011 13:37:39 -0800 [thread overview]
Message-ID: <20110222133739.d3e8da25.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20110222132303.6a78b8e0@queued.net>
On Tue, 22 Feb 2011 13:23:03 -0800 Andres Salomon wrote:
> I ran into a build error while attempting to build the Feb 22nd
> linux-next tree.
>
>
>
> From: Andres Salomon <dilinger@queued.net>
>
> Fix the following build error due to a missing semicolon:
>
> CC [M] drivers/spi/spi_altera.o
> drivers/spi/spi_altera.c:308: error: expected ‘,’ or ‘;’ before ‘extern’
> make[2]: *** [drivers/spi/spi_altera.o] Error 1
>
> Signed-off-by: Andres Salomon <dilinger@queued.net>
Acked-by: Randy Dunlap <randy.dunlap@oracle.com>
so ignore my combined patch. Thanks.
> ---
> drivers/spi/spi_altera.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/spi/spi_altera.c b/drivers/spi/spi_altera.c
> index 5e001f3..4813a63 100644
> --- a/drivers/spi/spi_altera.c
> +++ b/drivers/spi/spi_altera.c
> @@ -304,7 +304,7 @@ static int __devexit altera_spi_remove(struct platform_device *dev)
> static const struct of_device_id altera_spi_match[] = {
> { .compatible = "ALTR,spi-1.0", },
> {},
> -}
> +};
> MODULE_DEVICE_TABLE(of, altera_spi_match);
> #else /* CONFIG_OF */
> #define altera_spi_match NULL
> --
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2011-02-22 21:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 21:23 [PATCH] spi/spi_altera: fix build error Andres Salomon
2011-02-22 21:37 ` Randy Dunlap [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=20110222133739.d3e8da25.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=dbrownell@users.sourceforge.net \
--cc=dilinger@queued.net \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=spi-devel-general@lists.sourceforge.net \
/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).