From: Shawn Guo <shawn.guo@linaro.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
mturquette@linaro.org,
Fabio Estevam <fabio.estevam@freescale.com>
Subject: Re: [PATCH v2] clk: imx: clk-cpu: Include "clk.h" header file
Date: Thu, 7 May 2015 21:00:58 +0800 [thread overview]
Message-ID: <20150507130056.GI3162@dragon> (raw)
In-Reply-To: <1430343282-13739-1-git-send-email-festevam@gmail.com>
On Wed, Apr 29, 2015 at 06:34:42PM -0300, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@freescale.com>
>
> Include the "clk.h" header file to fix the following sparse warning:
>
> drivers/clk/imx/clk-cpu.c:77:12: warning: symbol 'imx_clk_cpu' was not declared. Should it be static?
>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] clk: imx: clk-cpu: Include "clk.h" header file
Date: Thu, 7 May 2015 21:00:58 +0800 [thread overview]
Message-ID: <20150507130056.GI3162@dragon> (raw)
In-Reply-To: <1430343282-13739-1-git-send-email-festevam@gmail.com>
On Wed, Apr 29, 2015 at 06:34:42PM -0300, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@freescale.com>
>
> Include the "clk.h" header file to fix the following sparse warning:
>
> drivers/clk/imx/clk-cpu.c:77:12: warning: symbol 'imx_clk_cpu' was not declared. Should it be static?
>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
Applied, thanks.
next prev parent reply other threads:[~2015-05-07 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 21:34 [PATCH v2] clk: imx: clk-cpu: Include "clk.h" header file Fabio Estevam
2015-04-29 21:34 ` Fabio Estevam
2015-05-07 13:00 ` Shawn Guo [this message]
2015-05-07 13:00 ` Shawn Guo
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=20150507130056.GI3162@dragon \
--to=shawn.guo@linaro.org \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@linaro.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.