From: Greg KH <gregkh@linuxfoundation.org>
To: Matei Oprea <eu@opreamatei.ro>
Cc: sachin.kamat@linaro.org, shaun@xresource.ca,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
ROSEdu Kernel Community <firefly@lists.rosedu.org>
Subject: Re: [PATCH] staging: cxt1e1: hwprobe: Fix sparse warning
Date: Tue, 18 Mar 2014 16:12:36 -0700 [thread overview]
Message-ID: <20140318231236.GA2327@kroah.com> (raw)
In-Reply-To: <1395181999-29433-1-git-send-email-eu@opreamatei.ro>
On Wed, Mar 19, 2014 at 12:33:19AM +0200, Matei Oprea wrote:
> This fixes the following sparse warning:
> * drivers/staging/cxt1e1/hwprobe.c:43:19:
> warning: symbol 'hdw_info' was not declared. Should it be static?
> * drivers/staging/cxt1e1/hwprobe.c:47:1:
> warning: symbol 'show_two' was not declared. Should it be static?
> * drivers/staging/cxt1e1/hwprobe.c:99:1:
> warning: symbol 'hdw_sn_get' was not declared. Should it be static?
> *drivers/staging/cxt1e1/hwprobe.c:149:1:
> warning: symbol 'prep_hdw_info' was not declared. Should it be static?
> * drivers/staging/cxt1e1/hwprobe.c:169:1:
> warning: symbol 'cleanup_ioremap' was not declared. Should it be static?
> * drivers/staging/cxt1e1/hwprobe.c:195:1:
> warning: symbol 'cleanup_devs' was not declared. Should it be static?
> drivers/staging/cxt1e1/hwprobe.c:293:1:
> * warning: symbol 'c4hw_attach_all' was not declared. Should it be static?
>
> Signed-off-by: Matei Oprea <eu@opreamatei.ro>
> Cc: ROSEdu Kernel Community <firefly@lists.rosedu.org>
Why the cc: for a non-maintainer / person?
curious,
greg k-h
next prev parent reply other threads:[~2014-03-18 23:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 22:33 [PATCH] staging: cxt1e1: hwprobe: Fix sparse warning Matei Oprea
2014-03-18 23:12 ` Greg KH [this message]
2014-03-19 5:43 ` [firefly] " Daniel Baluta
2014-03-18 23:12 ` Greg KH
2014-03-18 23:14 ` Greg KH
2014-03-21 9:46 ` Matei Oprea
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=20140318231236.GA2327@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=eu@opreamatei.ro \
--cc=firefly@lists.rosedu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sachin.kamat@linaro.org \
--cc=shaun@xresource.ca \
/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.