public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Jagan Teki <jteki@openedev.com>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
	Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH 2/2] dma: amba-pl08x: Fix line over 80 characters
Date: Thu, 21 May 2015 21:29:52 +0530	[thread overview]
Message-ID: <20150521155952.GS3140@localhost> (raw)
In-Reply-To: <1432149070-9569-2-git-send-email-jteki@openedev.com>

On Thu, May 21, 2015 at 12:41:10AM +0530, Jagan Teki wrote:
> This patch fixes line over 80 characters warninings while
> running checkpatch.pl
> 
> Signed-off-by: Jagan Teki <jteki@openedev.com>
> Cc: Dan Williams <dan.j.williams@intel.com>
> Cc: Vinod Koul <vinod.koul@intel.com>
> ---
>  drivers/dma/amba-pl08x.c | 13 +++++++++----
>  1 file changed, 9 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/dma/amba-pl08x.c b/drivers/dma/amba-pl08x.c
> index 49d396e..a5d9cc9 100644
> --- a/drivers/dma/amba-pl08x.c
> +++ b/drivers/dma/amba-pl08x.c
> @@ -646,7 +646,9 @@ static void pl08x_phy_alloc_and_start(struct pl08x_dma_chan *plchan)
>  
>  	ch = pl08x_get_phy_channel(pl08x, plchan);
>  	if (!ch) {
> -		dev_dbg(&pl08x->adev->dev, "no physical channel available for xfer on %s\n", plchan->name);
> +		dev_dbg(&pl08x->adev->dev,
> +			"no physical channel available for xfer on %s\n",
> +			plchan->name);
This looks bad to read including the below ones so I am going to decline it

-- 
~Vinod
>  		plchan->state = PL08X_CHAN_WAITING;
>  		return;
>  	}
> @@ -698,7 +700,8 @@ static void pl08x_phy_free(struct pl08x_dma_chan *plchan)
>  		}
>  
>  	if (!next) {
> -		list_for_each_entry(p, &pl08x->slave.channels, vc.chan.device_node)
> +		list_for_each_entry(p, &pl08x->slave.channels,
> +				vc.chan.device_node)

>  			if (p->state == PL08X_CHAN_WAITING) {
>  				next = p;
>  				break;
> @@ -1988,7 +1991,8 @@ static int pl08x_debugfs_show(struct seq_file *s, void *data)
>  	seq_printf(s, "\nPL08x virtual memcpy channels:\n");
>  	seq_printf(s, "CHANNEL:\tSTATE:\n");
>  	seq_printf(s, "--------\t------\n");
> -	list_for_each_entry(chan, &pl08x->memcpy.channels, vc.chan.device_node) {
> +	list_for_each_entry(chan, &pl08x->memcpy.channels,
> +			vc.chan.device_node) {
>  		seq_printf(s, "%s\t\t%s\n", chan->name,
>  			   pl08x_state_str(chan->state));
>  	}
> @@ -2172,7 +2176,8 @@ static int pl08x_probe(struct amba_device *adev, const struct amba_id *id)
>  			u32 val;
>  
>  			val = readl(ch->reg_config);
> -			if (val & (PL080N_CONFIG_ITPROT | PL080N_CONFIG_SECPROT)) {
> +			if (val & (PL080N_CONFIG_ITPROT |
> +					PL080N_CONFIG_SECPROT)) {
>  				dev_info(&adev->dev, "physical channel %d reserved for secure access only\n", i);
>  				ch->locked = true;
>  			}
> -- 
> 1.9.1
> 

-- 

  reply	other threads:[~2015-05-21 15:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20 19:11 [PATCH 1/2] dma: omap-dma: Fix line over 80 characters Jagan Teki
2015-05-20 19:11 ` [PATCH 2/2] dma: amba-pl08x: " Jagan Teki
2015-05-21 15:59   ` Vinod Koul [this message]
2015-05-20 20:24 ` [PATCH 1/2] dma: omap-dma: " Joe Perches
2015-05-21 15:59 ` Vinod Koul
2015-05-21 16:40   ` Joe Perches

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=20150521155952.GS3140@localhost \
    --to=vinod.koul@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=jteki@openedev.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