From: Johannes Berg <johannes@sipsolutions.net>
To: Sachin Kamat <sachin.kamat@linaro.org>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
davem@davemloft.net, linville@tuxdriver.com
Subject: Re: [PATCH 1/1] net: rfkill: Fix sparse warning in rfkill-regulator.c
Date: Wed, 20 Feb 2013 11:09:31 +0100 [thread overview]
Message-ID: <1361354971.8629.18.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1361354928.8629.17.camel@jlt4.sipsolutions.net> (sfid-20130220_110906_640334_BAA70538)
On Wed, 2013-02-20 at 11:08 +0100, Johannes Berg wrote:
> On Tue, 2013-02-19 at 15:27 +0530, Sachin Kamat wrote:
> > 'rfkill_regulator_ops' is used only in this file. Hence make it static.
> > Silences the following warning:
> > net/rfkill/rfkill-regulator.c:54:19: warning:
> > symbol 'rfkill_regulator_ops' was not declared. Should it be static?
>
> I'll take this, but it isn't going anywhere until the merge window opens
> again.
Err, I mean closes, and we open -next.
johannes
prev parent reply other threads:[~2013-02-20 10:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 9:57 [PATCH 1/1] net: rfkill: Fix sparse warning in rfkill-regulator.c Sachin Kamat
2013-02-20 10:08 ` Johannes Berg
2013-02-20 10:09 ` Johannes Berg [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=1361354971.8629.18.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=sachin.kamat@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox