From: elezegarcia@gmail.com (Ezequiel García)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [QUESTION] staging/easycap fix
Date: Tue, 14 Feb 2012 01:47:52 -0300 [thread overview]
Message-ID: <CALF0-+Ue+MBB531WgsQNjCBdkPe=tSLB1fAcyfX-Wa_o_rZAGg@mail.gmail.com> (raw)
In-Reply-To: <CALF0-+UdbqOnQ6ZT0bPiMVCTFWwMQss6XrFqNL6xsugRPVX_qw@mail.gmail.com>
Hi,
I'm try to fix staging/easycap driver. I know it has some bugs
somewhere (I've seen some panics while using the device) but
I wanted to improve the code style before debugging it. In the
meantime, I expect to develop a better understanding of the code.
However, I want know if I am in the right direction; so I want to know
if this is ok:
1. mainly I am splitting very large functions into smaller parts. ?For
instance, xxx_probe function is +1k lines long, so I'm
splitting it up to make the code cleaner, more readable. Is this ok?
2. second, I am fixing some style issues (besides checkpatch), for
instance "if" syntax:
- ? if (0 == bInterfaceNumber) {
+ ? if (bInterfaceNumber == 0) {
and ugly comments like:
-/*---------------------------------------------------------------------------*/
-/*
- * ?GET PROPERTIES OF PROBED INTERFACE
- */
-/*---------------------------------------------------------------------------*/
+
+ ? /*
+ ? ?* ?GET PROPERTIES OF PROBED INTERFACE
+ ? ?*/
So, Am I on the right track?
Thanks,
Ezequiel.
next parent reply other threads:[~2012-02-14 4:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALF0-+UdbqOnQ6ZT0bPiMVCTFWwMQss6XrFqNL6xsugRPVX_qw@mail.gmail.com>
2012-02-14 4:47 ` Ezequiel García [this message]
2012-02-14 5:06 ` [QUESTION] staging/easycap fix Greg KH
2012-02-14 5:30 ` Ezequiel García
2012-02-14 5:59 ` Manavendra Nath Manav
2012-02-14 6:26 ` Greg KH
2012-02-14 22:01 ` Ezequiel García
2012-02-14 22:39 ` Greg KH
2012-02-15 14:14 ` Peter Senna Tschudin
2012-02-16 12:57 ` Ezequiel García
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='CALF0-+Ue+MBB531WgsQNjCBdkPe=tSLB1fAcyfX-Wa_o_rZAGg@mail.gmail.com' \
--to=elezegarcia@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).