From: Devendra Naga <develkernel412222@gmail.com>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
"Mikko Virkkilä" <mikko.virkkila@bluegiga.com>,
"Lauri Hintsala" <Lauri.Hintsala@bluegiga.com>,
"Riku Mettälä" <riku.mettala@bluegiga.com>,
"Veli-Pekka Peltola" <veli-pekka.peltola@bluegiga.com>
Cc: Devendra Naga <develkernel412222@gmail.com>
Subject: [PATCH 0/5] staging/csr: cleanup patches
Date: Sat, 4 Aug 2012 13:00:08 +0545 [thread overview]
Message-ID: <1344064508-11975-1-git-send-email-develkernel412222@gmail.com> (raw)
Hi Greg,
These patches does
* coding style fixes
* little cleanups like unneeded initialisations and
comparing a bool against 1 in if
each and every patch is compile tested on top of the previous one
Thanks,
----------------------------
Actually i have a question about the dbg macros, unifi_warning,
unifi_error, and unifi_trace,
I think these can be implemented using dev_warn, dev_dbg, functions,
i mean we can remove these unifi_warning and unifi_error and unifi_trace
and use the dev_warn and dev_dbg.
Please correct me if i am wrong
Devendra Naga (5):
staging/csr: clean coding style in uf_start_thread
staging/csr: fix coding style problems in uf_stop_thread
staging/csr: fix coding style problems in uf_wait_for_thread_to_stop
staging/csr: remove the initialisation of interfaceTag and its
comment in handle_bh_error
staging/csr: fix coding style problems in handle_bh_error
drivers/staging/csr/bh.c | 173 ++++++++++++++++++++++++----------------------
1 file changed, 90 insertions(+), 83 deletions(-)
Signed-off-by: Devendra Naga <develkernel412222@gmail.com>
--
1.7.9.5
next reply other threads:[~2012-08-04 7:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-04 7:15 Devendra Naga [this message]
2012-08-14 1:58 ` [PATCH 0/5] staging/csr: cleanup patches 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=1344064508-11975-1-git-send-email-develkernel412222@gmail.com \
--to=develkernel412222@gmail.com \
--cc=Lauri.Hintsala@bluegiga.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikko.virkkila@bluegiga.com \
--cc=riku.mettala@bluegiga.com \
--cc=veli-pekka.peltola@bluegiga.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