From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: S3C64XX: Prototype SPI devices
Date: Wed, 08 Sep 2010 21:39:21 +0900 [thread overview]
Message-ID: <004201cb4f52$df6e6e20$9e4b4a60$%kim@samsung.com> (raw)
In-Reply-To: <1283941539-3892-2-git-send-email-broonie@opensource.wolfsonmicro.com>
Mark Brown wrote:
>
> Avoids build warnings due to the undeclared non-statics.
>
Could you please let me know what's the build warning?
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> arch/arm/mach-s3c64xx/dev-spi.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-s3c64xx/dev-spi.c
b/arch/arm/mach-s3c64xx/dev-spi.c
> index bfa3ef7..405e621 100644
> --- a/arch/arm/mach-s3c64xx/dev-spi.c
> +++ b/arch/arm/mach-s3c64xx/dev-spi.c
> @@ -22,6 +22,7 @@
>
> #include <plat/s3c64xx-spi.h>
> #include <plat/gpio-cfg.h>
> +#include <plat/devs.h>
>
> static char *spi_src_clks[] = {
> [S3C64XX_SPI_SRCCLK_PCLK] = "pclk",
> --
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
next prev parent reply other threads:[~2010-09-08 12:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 10:25 [PATCH 1/2] ARM: S3C64XX: Fix dev-spi build Mark Brown
2010-09-08 10:25 ` [PATCH 2/2] ARM: S3C64XX: Prototype SPI devices Mark Brown
2010-09-08 12:39 ` Kukjin Kim [this message]
2010-09-08 12:46 ` Mark Brown
2010-09-09 11:18 ` Kukjin Kim
2010-09-09 11:33 ` Mark Brown
2010-09-08 11:52 ` [PATCH 1/2] ARM: S3C64XX: Fix dev-spi build Kukjin Kim
2010-09-08 12:12 ` Mark Brown
2010-09-08 12:21 ` Kukjin Kim
2010-09-08 14:17 ` Jassi Brar
2010-09-08 16:01 ` Mark Brown
2010-09-09 1:17 ` Jassi Brar
2010-09-09 11:11 ` Kukjin Kim
2010-09-09 11:34 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2010-08-20 15:38 Mark Brown
2010-08-20 15:39 ` [PATCH 2/2] ARM: S3C64XX: Prototype SPI devices Mark Brown
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='004201cb4f52$df6e6e20$9e4b4a60$%kim@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.