From: Krzysztof Kozlowski <k.kozlowski.k@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Kukjin Kim <kgene@kernel.org>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH] ARM: s3c64xx: smartq: Avoid sparse warnings
Date: Mon, 11 Jul 2016 17:47:19 +0200 [thread overview]
Message-ID: <20160711154719.GA7702@kozik-lap> (raw)
In-Reply-To: <20160711084836.12835-1-thierry.reding@gmail.com>
On Mon, Jul 11, 2016 at 10:48:36AM +0200, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> The smartq_map_io() and smartq_machine_init() functions are used by both
> SmartQ 5 and SmartQ 7 machines and exported via the mach-smartq.h header
> file. However that header file is not included by the mach-smartq.c file
> that implements them, causing sparse warnings.
>
> Include mach-smartq.h from mach-smartq.c to fix these warnings.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> arch/arm/mach-s3c64xx/mach-smartq.c | 1 +
> 1 file changed, 1 insertion(+)
>
Thanks, applied.
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: k.kozlowski.k@gmail.com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: s3c64xx: smartq: Avoid sparse warnings
Date: Mon, 11 Jul 2016 17:47:19 +0200 [thread overview]
Message-ID: <20160711154719.GA7702@kozik-lap> (raw)
In-Reply-To: <20160711084836.12835-1-thierry.reding@gmail.com>
On Mon, Jul 11, 2016 at 10:48:36AM +0200, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> The smartq_map_io() and smartq_machine_init() functions are used by both
> SmartQ 5 and SmartQ 7 machines and exported via the mach-smartq.h header
> file. However that header file is not included by the mach-smartq.c file
> that implements them, causing sparse warnings.
>
> Include mach-smartq.h from mach-smartq.c to fix these warnings.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> arch/arm/mach-s3c64xx/mach-smartq.c | 1 +
> 1 file changed, 1 insertion(+)
>
Thanks, applied.
Best regards,
Krzysztof
next prev parent reply other threads:[~2016-07-11 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 8:48 [PATCH] ARM: s3c64xx: smartq: Avoid sparse warnings Thierry Reding
2016-07-11 8:48 ` Thierry Reding
2016-07-11 15:47 ` Krzysztof Kozlowski [this message]
2016-07-11 15:47 ` Krzysztof Kozlowski
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=20160711154719.GA7702@kozik-lap \
--to=k.kozlowski.k@gmail.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=thierry.reding@gmail.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 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.