From: 'Tejun Heo' <tj@kernel.org>
To: Jingoo Han <jg1.han@samsung.com>
Cc: linux-ide@vger.kernel.org, Viresh Kumar <viresh.linux@gmail.com>
Subject: Re: [PATCH 1/2] ata: pata_arasan: Staticize local symbols
Date: Fri, 9 Aug 2013 10:13:25 -0400 [thread overview]
Message-ID: <20130809141325.GE20515@mtj.dyndns.org> (raw)
In-Reply-To: <000001ce94c2$30c95430$925bfc90$@samsung.com>
On Fri, Aug 09, 2013 at 02:35:00PM +0900, Jingoo Han wrote:
> These local symbols are used only in this file.
> Fix the following sparse warnings:
>
> drivers/ata/pata_arasan_cf.c:657:6: warning: symbol 'arasan_cf_error_handler' was not declared. Should it be static?
> drivers/ata/pata_arasan_cf.c:686:14: warning: symbol 'arasan_cf_qc_issue' was not declared. Should it be static?
>
> Signed-off-by: Jingoo Han <jg1.han@samsung.com>
Applied to libata/for-3.12.
Thanks.
--
tejun
prev parent reply other threads:[~2013-08-09 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 5:35 [PATCH 1/2] ata: pata_arasan: Staticize local symbols Jingoo Han
2013-08-09 5:41 ` Viresh Kumar
2013-08-09 14:13 ` 'Tejun Heo' [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=20130809141325.GE20515@mtj.dyndns.org \
--to=tj@kernel.org \
--cc=jg1.han@samsung.com \
--cc=linux-ide@vger.kernel.org \
--cc=viresh.linux@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 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).