kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [QUESTION] staging/easycap fix
Date: Mon, 13 Feb 2012 21:06:33 -0800	[thread overview]
Message-ID: <20120214050633.GA30972@kroah.com> (raw)
In-Reply-To: <CALF0-+Ue+MBB531WgsQNjCBdkPe=tSLB1fAcyfX-Wa_o_rZAGg@mail.gmail.com>

On Tue, Feb 14, 2012 at 01:47:52AM -0300, Ezequiel Garc?a wrote:
> 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?

Yes.

> 2. second, I am fixing some style issues (besides checkpatch), for
> instance "if" syntax:
> 
> - ? if (0 == bInterfaceNumber) {
> + ? if (bInterfaceNumber == 0) {

You do know why the first style was chosen, right?  That's not saying
your change is incorrect, but odds are, there are bigger things that
need to be fixed up first.

> and ugly comments like:
> 
> -/*---------------------------------------------------------------------------*/
> -/*
> - * ?GET PROPERTIES OF PROBED INTERFACE
> - */
> -/*---------------------------------------------------------------------------*/
> +
> + ? /*
> + ? ?* ?GET PROPERTIES OF PROBED INTERFACE
> + ? ?*/
> 
> So, Am I on the right track?

Close, how about:
	/* Get properties of probed interface */
instead?

thanks,

greg k-h

  reply	other threads:[~2012-02-14  5:06 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 ` [QUESTION] staging/easycap fix Ezequiel García
2012-02-14  5:06   ` Greg KH [this message]
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=20120214050633.GA30972@kroah.com \
    --to=greg@kroah.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).