From: Greg KH <gregkh@linuxfoundation.org>
To: Matei Oprea <eu@opreamatei.ro>
Cc: devel@driverdev.osuosl.org,
ROSEdu Kernel Community <firefly@lists.rosedu.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8192u: r8192U_wx: Fix sparse warnings
Date: Fri, 18 Apr 2014 16:02:00 -0700 [thread overview]
Message-ID: <20140418230200.GA966@kroah.com> (raw)
In-Reply-To: <1395410869-19362-1-git-send-email-eu@opreamatei.ro>
On Fri, Mar 21, 2014 at 04:07:49PM +0200, Matei Oprea wrote:
> Fix sparse "should be static" warnings. Those structures are
> only referenced in file scope so they can be marked as static.
>
> Signed-off-by: Matei Oprea <eu@opreamatei.ro>
> Cc: ROSEdu Kernel Community <firefly@lists.rosedu.org>
> ---
> drivers/staging/rtl8192u/r8192U_wx.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
This patch breaks the build, how did you test it?
prev parent reply other threads:[~2014-04-18 23:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 14:07 [PATCH] staging: rtl8192u: r8192U_wx: Fix sparse warnings Matei Oprea
2014-04-18 23:02 ` Greg KH [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=20140418230200.GA966@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 \
/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