From: Joel Pelaez Jorge <joelpelaez@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Silvan Jegen <s.jegen@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] Staging: rtl8192e: Fix code issues
Date: Sun, 06 Apr 2014 16:25:23 -0500 [thread overview]
Message-ID: <5341C643.4050700@gmail.com> (raw)
In the kernel driver: rtl8192e, exists some problems related
to source check, using the tool sparse, but for fix it, is necessary
remove a bad declaration that keep off the patch.
Because it is resolved before apply the "main" patch.
Joel Pelaez Jorge (2):
Staging: rtl8192e: Remove bad 'extern' declaration
Staging: rtl8192e: Fix sparse warning
drivers/staging/rtl8192e/rtl8192e/rtl_wx.c | 1 +
drivers/staging/rtl8192e/rtl8192e/rtl_wx.h | 1 -
2 files changed, 1 insertion(+), 1 deletion(-)
--
1.9.1
--
next reply other threads:[~2014-04-06 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-06 21:25 Joel Pelaez Jorge [this message]
2014-04-06 21:29 ` [PATCH 1/2] Staging: rtl8192e: Remove bad 'extern' declaration Joel Pelaez Jorge
2014-04-06 21:30 ` [PATCH 2/2] Staging: rtl8192e: Fix sparse warning Joel Pelaez Jorge
2014-04-06 21:43 ` Joe Perches
2014-04-07 0:38 ` [PATCH 0/3] Staging: rtl8192e: Fix code issues Greg Kroah-Hartman
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=5341C643.4050700@gmail.com \
--to=joelpelaez@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.jegen@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).