public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Johan Meiring <johanmeiring@gmail.com>
Cc: gregkh@linuxfoundation.org, a.beregalov@gmail.com,
	devendra.aaru@gmail.com, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 06/10] staging: cxt1e1: musycc.c: fixes placement of parentheses
Date: Wed, 21 Nov 2012 12:07:49 +0300	[thread overview]
Message-ID: <20121121090749.GF11248@mwanda> (raw)
In-Reply-To: <1353432532-21203-6-git-send-email-johanmeiring@gmail.com>

On Tue, Nov 20, 2012 at 07:28:48PM +0200, Johan Meiring wrote:
> This commit fixes several incorrect placements of parantheses, as
> identified by the checkpatch.pl tool.
> 

This patch is fine, and all.
Acked-by: Dan Carpenter <dan.carpenter@oracle.com>

But you could go beyond fixing just checkpatch.pl warnings.

> Signed-off-by: Johan Meiring <johanmeiring@gmail.com>
> ---
>  drivers/staging/cxt1e1/musycc.c |  490 +++++++++++++++++++--------------------
>  1 file changed, 245 insertions(+), 245 deletions(-)
> 
> diff --git a/drivers/staging/cxt1e1/musycc.c b/drivers/staging/cxt1e1/musycc.c
> index 42e1ca4..b2cc68a 100644
> --- a/drivers/staging/cxt1e1/musycc.c
> +++ b/drivers/staging/cxt1e1/musycc.c
> @@ -60,21 +60,21 @@ extern ci_t *CI;                /* dummy pointr to board ZEROE's data - DEBUG
>  
>  /*******************************************************************/

This line could be deleted.

>  /* forward references */

Obvious comment is obvious.

> -void        c4_fifo_free (mpi_t *, int);
> -void        c4_wk_chan_restart (mch_t *);
> -void        musycc_bh_tx_eom (mpi_t *, int);
> -int         musycc_chan_up (ci_t *, int);
> -status_t __init musycc_init (ci_t *);
> -STATIC void __init musycc_init_port (mpi_t *);
> -void        musycc_intr_bh_tasklet (ci_t *);
> -void        musycc_serv_req (mpi_t *, u_int32_t);
> -void        musycc_update_timeslots (mpi_t *);
> +void        c4_fifo_free(mpi_t *, int);
> +void        c4_wk_chan_restart(mch_t *);
> +void        musycc_bh_tx_eom(mpi_t *, int);
> +int         musycc_chan_up(ci_t *, int);
> +status_t __init musycc_init(ci_t *);
> +STATIC void __init musycc_init_port(mpi_t *);
> +void        musycc_intr_bh_tasklet(ci_t *);
> +void        musycc_serv_req(mpi_t *, u_int32_t);
> +void        musycc_update_timeslots(mpi_t *);


These would look better done properly.

void musycc_serv_req(mpi_t *pi, u_int32_t req);

Keep the parameter names because they serve as documentation.  And
actually, they should be moved to a header file which is included
instead of declared in the .c files where they are used.

regards,
dan carpenter


  reply	other threads:[~2012-11-21  9:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-20 17:28 [PATCH 01/10] staging: cxt1e1: musycc.h: fixes indentation issues Johan Meiring
2012-11-20 17:28 ` [PATCH 02/10] staging: cxt1e1: musycc.h: fixes coding style issues Johan Meiring
2012-11-20 17:28 ` [PATCH 03/10] staging: cxt1e1: musycc.h: fixes brace placement Johan Meiring
2012-11-20 17:28 ` [PATCH 04/10] staging: cxt1e1: musycc.c: uses tabs for indentation Johan Meiring
2012-11-20 17:28 ` [PATCH 05/10] staging: cxt1e1: musycc.c: fixes brace placement Johan Meiring
2012-11-20 17:28 ` [PATCH 06/10] staging: cxt1e1: musycc.c: fixes placement of parentheses Johan Meiring
2012-11-21  9:07   ` Dan Carpenter [this message]
2012-11-20 17:28 ` [PATCH 07/10] staging: cxt1e1: sbecrc.c: fixes indentation issues Johan Meiring
2012-11-20 17:28 ` [PATCH 08/10] staging: cxt1e1: sbecrc.c: fixes brace placement Johan Meiring
2012-11-20 17:28 ` [PATCH 09/10] staging: cxt1e1: sbecrc.c: fixes coding style issue Johan Meiring
2012-11-20 17:28 ` [PATCH 10/10] staging: cxt1e1: sbecrc.c: fixes 80+ char line length issue Johan Meiring
2012-11-21  9:04   ` Dan Carpenter

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=20121121090749.GF11248@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=a.beregalov@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=devendra.aaru@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=johanmeiring@gmail.com \
    --cc=linux-kernel@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