From: Jeff Oczek <jeffoczek@gmail.com>
To: gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Jeff Oczek <jeffoczek@gmail.com>
Subject: [PATCH v2 0/2] staging: cxt1e1: Fix ambiguous global var names, reduce sparse warnings
Date: Tue, 22 Jul 2014 20:34:54 -0400 [thread overview]
Message-ID: <1406075696-15912-1-git-send-email-jeffoczek@gmail.com> (raw)
In-Reply-To: <1406059671-6536-1-git-send-email-jeffoczek@gmail.com>
This patch set:
changes ambiguous global names, such as "error_flag" to "cxt1e1_error_flag"
puts globals in header file to reduce externs used in c files as well as sparse warnings
Jeff Oczek (2):
staging: cxt1e1: Prefix ambiguous variable names with 'cxt1e1_' for
clarity
staging: cxt1e1: Fix static symbol sparse warnings for global vars in
linux.c
drivers/staging/cxt1e1/cxt1e1_common.h | 14 +++++++++
drivers/staging/cxt1e1/hwprobe.c | 7 +++--
drivers/staging/cxt1e1/linux.c | 54 +++++++++++++++++++---------------
drivers/staging/cxt1e1/musycc.c | 5 +---
drivers/staging/cxt1e1/pmcc4_drv.c | 23 +++++++--------
drivers/staging/cxt1e1/sbeproc.c | 6 ++--
6 files changed, 64 insertions(+), 45 deletions(-)
create mode 100644 drivers/staging/cxt1e1/cxt1e1_common.h
--
1.9.1
next prev parent reply other threads:[~2014-07-23 0:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 20:07 [PATCH] staging: cxt1e1: Fix static symbol sparse warnings for global vars in linux.c Jeff Oczek
2014-07-22 20:17 ` Greg KH
2014-07-22 20:56 ` Jeff Oczek
2014-07-22 21:23 ` Greg KH
2014-07-23 0:34 ` Jeff Oczek [this message]
2014-07-23 0:34 ` [PATCH v2 1/2] staging: cxt1e1: Prefix ambiguous variable names with 'cxt1e1_' for clarity Jeff Oczek
2014-07-23 0:34 ` [PATCH v2 2/2] staging: cxt1e1: Fix static symbol sparse warnings for global vars in linux.c Jeff Oczek
2014-07-24 1:20 ` [PATCH v2 1/2] staging: cxt1e1: Prefix ambiguous variable names with 'cxt1e1_' for clarity Greg KH
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=1406075696-15912-1-git-send-email-jeffoczek@gmail.com \
--to=jeffoczek@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.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
Powered by JetHome