From: Dan Carpenter <dan.carpenter@oracle.com>
To: Marcos Paulo de Souza <marcos.mage@gmail.com>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
Greg Kroah-Hartman <gregkh@suse.de>,
Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: [PATCH 3/3] staging: vt6655: card.c, srom.c, vntwifi.c: Code cleanup
Date: Sat, 3 Dec 2011 11:32:15 +0300 [thread overview]
Message-ID: <20111203083215.GF3195@mwanda> (raw)
In-Reply-To: <1322855892-6400-1-git-send-email-marcos.mage@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
On Fri, Dec 02, 2011 at 07:58:12PM +0000, Marcos Paulo de Souza wrote:
> This patch removes commented code, useless comments, blank lines and fix
> coding style of the headers of functions.
>
> Signed-off-by: Marcos Paulo de Souza <marcos.mage@gmail.com>
> Cc: Greg Kroah-Hartman <gregkh@suse.de>
> Cc: devel@driverdev.osuosl.org
> ---
> /*
> - * Description: Test if bits off in eeprom
> - *
> - * Parameters:
> - * In:
> - * dwIoBase - I/O base address
> - * byContntOffset - address of EEPROM
> - * byTestBits - bits to test
> - * Out:
> - * none
> - *
> - * Return Value: true if all test bits off; otherwise false
> - *
> + * Test if bits off in eeprom
> */
Some of these seems sort of useful. It might be better to change
them to doc-book format instead of deleting them:
/**
* SROMbIsRegBitsOff() - Test if bits off in eeprom
* @dwIoBase: I/O base address
* @byContntOffset: Address of EEPROM
* @byTestBits: Bits to test
*
* Returns true if all test bits off; otherwise false.
*/
There is a howto in Documentation/kernel-doc-nano-HOWTO.txt.
regards,
dan carpenter
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-12-03 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 19:58 [PATCH 3/3] staging: vt6655: card.c, srom.c, vntwifi.c: Code cleanup Marcos Paulo de Souza
2011-12-03 8:32 ` Dan Carpenter [this message]
2011-12-04 22:01 ` Marcos Paulo de Souza
2011-12-08 19:25 ` 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=20111203083215.GF3195@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcos.mage@gmail.com \
--cc=rdunlap@xenotime.net \
/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