All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Daeseok Youn <daeseok.youn@gmail.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
	shaun@xresource.ca, sachin.kamat@linaro.org,
	linux-kernel@vger.kernel.org, dulshani.gunawardhana89@gmail.com,
	ying.xue@windriver.com, davem@davemloft.net
Subject: Re: [PATCH 3/7] staging: cxt1e1: Fix line length over 80 characters in linux.c
Date: Tue, 4 Mar 2014 11:45:56 +0300	[thread overview]
Message-ID: <20140304084555.GS26722@mwanda> (raw)
In-Reply-To: <2825545.2YpN0JuVSn@daeseok-laptop.cloud.net>

On Tue, Mar 04, 2014 at 11:08:46AM +0900, Daeseok Youn wrote:
> 
> clean up checkpatch.pl warnings:
>  WARNING: Line length over 80 characters
> 
> Signed-off-by: Daeseok Youn <daeseok.youn@gmail.com>
> ---
>  drivers/staging/cxt1e1/linux.c |   48 +++++++++++++++++++++++++--------------
>  1 files changed, 31 insertions(+), 17 deletions(-)
> 
> diff --git a/drivers/staging/cxt1e1/linux.c b/drivers/staging/cxt1e1/linux.c
> index 17d73f4..579e68e 100644
> --- a/drivers/staging/cxt1e1/linux.c
> +++ b/drivers/staging/cxt1e1/linux.c
> @@ -31,7 +31,7 @@
>  #include "pmcc4_private.h"
>  #include "sbeproc.h"
>  
> -/*****************************************************************************************
> +/*******************************************************************************

This should just be:

/*
 *
 *

Not ************************************************** etc.

Fix in a later patch if you want.

regards,
dan carpenter



  parent reply	other threads:[~2014-03-04  8:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04  2:08 [PATCH 3/7] staging: cxt1e1: Fix line length over 80 characters in linux.c Daeseok Youn
2014-03-04  3:24 ` Joe Perches
2014-03-04  5:01   ` DaeSeok Youn
2014-03-04  8:45 ` Dan Carpenter [this message]
2014-03-04 10:10   ` DaeSeok Youn

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=20140304084555.GS26722@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=daeseok.youn@gmail.com \
    --cc=davem@davemloft.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=dulshani.gunawardhana89@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sachin.kamat@linaro.org \
    --cc=shaun@xresource.ca \
    --cc=ying.xue@windriver.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.