From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [Patch] Driver: Staging: checkpatch cleanup for drivers/staging/winbond/wb35tx_s.h
Date: Tue, 25 Sep 2012 20:51:43 +0000 [thread overview]
Message-ID: <20120925205143.GW4587@mwanda> (raw)
In-Reply-To: <506210B8.7000604@gmail.com>
On Wed, Sep 26, 2012 at 01:44:48AM +0530, Harsh Kumar wrote:
> checkpatch cleanup for drivers/staging/winbond/wb35tx_s.h
>
> 1) Changed c99 comments to c89 comments
> 2) Removed undesired spaces which were causing checkpatch errors.
>
Can you break this up into two patches.
This doesn't apply for me on linux-next (please redo it so it
applies).
> Signed-off-by: Harsh Kumar <harsh1kumar@gmail.com>
>
> diff -uprN a/drivers/staging/winbond/wb35tx_s.h b/drivers/staging/winbond/wb35tx_s.h
> --- a/drivers/staging/winbond/wb35tx_s.h
> +++ b/drivers/staging/winbond/wb35tx_s.h
> @@ -3,45 +3,45 @@
>
> #include "mds_s.h"
>
> -//==================
> -// IS89C35 Tx related definition
> -//==================
> -#define TX_INTERFACE 0 // Interface 1
> -#define TX_PIPE 3 // endpoint 4
> -#define TX_INTERRUPT 1 // endpoint 2
> -#define MAX_INTERRUPT_LENGTH 64 // It must be 64 for EP2 hardware
> +/**********************************
> +* IS89C35 Tx related definition
> +***********************************/
Just make these a normal comments.
/* IS89C35 Tx related definitions */
Or for multi-line:
/*
* IS89C35 Tx related blah blah blha blah blah blah blah blha blah
* definitions
*/
There is a section on comments in CodingStyle.
> +#define TX_INTERFACE 0 /* Interface 1 */
> +#define TX_PIPE 3 /* Endpoint 4 */
> +#define TX_INTERRUPT 1 /* Endpoint 2 */
> +#define MAX_INTERRUPT_LENGTH 64 /* It must be 64 for EP2 hardware */
>
>
>
Only one blank line at a time. (Although that was there in the
original so that's fine).
> -//==================
> -// Internal variable for module
> -//==================
> +/**********************************
> +* Internal variable for module
> +***********************************/
>
>
> struct wb35_tx {
> - // For Tx buffer
> - u8 TxBuffer[ MAX_USB_TX_BUFFER_NUMBER ][ MAX_USB_TX_BUFFER ];
> + /* For Tx buffer */
> + u8 TxBuffer[MAX_USB_TX_BUFFER_NUMBER][MAX_USB_TX_BUFFER];
>
> - // For Interrupt pipe
> + /* For Interrupt pipe */
> u8 EP2_buf[MAX_INTERRUPT_LENGTH];
>
> - atomic_t TxResultCount;// For thread control of EP2 931130.4.m
> - atomic_t TxFireCounter;// For thread control of EP4 931130.4.n
> - u32 ByteTransfer;
> -
> - u32 TxSendIndex;// The next index of Mds array to be sent
> - u32 EP2vm_state; // for EP2vm state
> - u32 EP4vm_state; // for EP4vm state
> - u32 tx_halt; // Stopping VM
> + atomic_t TxResultCount;/* For thread control of EP2 931130.4.m */
^
Put a space there, between the semi-colon and the comment.
regards,
dan carpenter
next prev parent reply other threads:[~2012-09-25 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 20:26 [Patch] Driver: Staging: checkpatch cleanup for drivers/staging/winbond/wb35tx_s.h Harsh Kumar
2012-09-25 20:51 ` Dan Carpenter [this message]
2012-09-26 3:51 ` Harsh Kumar
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=20120925205143.GW4587@mwanda \
--to=dan.carpenter@oracle.com \
--cc=kernel-janitors@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