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 1/2] dma: omap-dma: Fix line over 80 characters
Date: Thu, 21 May 2015 21:29:34 +0530	[thread overview]
Message-ID: <20150521155934.GR3140@localhost> (raw)
In-Reply-To: <1432149070-9569-1-git-send-email-jteki@openedev.com>

On Thu, May 21, 2015 at 12:41:09AM +0530, Jagan Teki wrote:
> This patch fixes line over 80 characters warninings while
> running checkpatch.pl

You should know 80 char is a warn not an error, and you should read the
Codingstyle documentation before you embark on these changes.
The guiding principle here is readablity and greapblity, anything which
breaks these is strict NO.
> 
> 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/omap-dma.c | 18 ++++++++++++------
>  1 file changed, 12 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/dma/omap-dma.c b/drivers/dma/omap-dma.c
> index 167dbaf..3806524 100644
> --- a/drivers/dma/omap-dma.c
> +++ b/drivers/dma/omap-dma.c
> @@ -168,7 +168,8 @@ static inline struct omap_chan *to_omap_dma_chan(struct dma_chan *c)
>  	return container_of(c, struct omap_chan, vc.chan);
>  }
>  
> -static inline struct omap_desc *to_omap_dma_desc(struct dma_async_tx_descriptor *t)
> +static inline struct omap_desc *to_omap_dma_desc(
> +				struct dma_async_tx_descriptor *t)
This makes it harder to read, if you see drivers the will do it:

static inline struct omap_desc
*to_omap_dma_desc(struct dma_async_tx_descriptor *t)


>  {
>  	return container_of(t, struct omap_desc, vd.tx);
>  }
> @@ -219,7 +220,8 @@ static unsigned omap_dma_read(unsigned type, void __iomem *addr)
>  	return val;
>  }
>  
> -static void omap_dma_glbl_write(struct omap_dmadev *od, unsigned reg, unsigned val)
> +static void omap_dma_glbl_write(struct omap_dmadev *od,
> +				unsigned reg, unsigned val)
>  {
>  	const struct omap_dma_reg *r = od->reg_map + reg;
>  
> @@ -334,7 +336,7 @@ static void omap_dma_stop(struct omap_chan *c)
>  		if (val & (CCR_RD_ACTIVE | CCR_WR_ACTIVE))
>  			dev_err(c->vc.chan.device->dev,
>  				"DMA drain did not complete on lch %d\n",
> -			        c->dma_ch);
> +				c->dma_ch);
whats changes here? title says 80 char!

>  
>  		omap_dma_glbl_write(od, OCP_SYSCONFIG, sysconfig);
>  	} else {
> @@ -544,7 +546,8 @@ static int omap_dma_alloc_chan_resources(struct dma_chan *chan)
>  			val = BIT(c->dma_ch);
>  			omap_dma_glbl_write(od, IRQSTATUS_L1, val);
>  			od->irq_enable_mask |= val;
> -			omap_dma_glbl_write(od, IRQENABLE_L1, od->irq_enable_mask);
> +			omap_dma_glbl_write(od, IRQENABLE_L1,
> +						od->irq_enable_mask);
>  
>  			val = omap_dma_glbl_read(od, IRQENABLE_L0);
>  			val &= ~BIT(c->dma_ch);
> @@ -707,7 +710,8 @@ static enum dma_status omap_dma_tx_status(struct dma_chan *chan,
>  	spin_lock_irqsave(&c->vc.lock, flags);
>  	vd = vchan_find_desc(&c->vc, cookie);
>  	if (vd) {
> -		txstate->residue = omap_dma_desc_size(to_omap_dma_desc(&vd->tx));
> +		txstate->residue = omap_dma_desc_size(
> +						to_omap_dma_desc(&vd->tx));
>  	} else if (c->desc && c->desc->vd.tx.cookie == cookie) {
>  		struct omap_desc *d = c->desc;
>  		dma_addr_t pos;
> @@ -741,6 +745,7 @@ static void omap_dma_issue_pending(struct dma_chan *chan)
>  		 */
>  		if (!c->cyclic) {
>  			struct omap_dmadev *d = to_omap_dma_dev(chan->device);
> +
this is not per title

-- 
~Vinod
>  			spin_lock(&d->lock);
>  			if (list_empty(&c->node))
>  				list_add_tail(&c->node, &d->pending);
> @@ -948,7 +953,8 @@ static struct dma_async_tx_descriptor *omap_dma_prep_dma_cyclic(
>  	return vchan_tx_prep(&c->vc, &d->vd, flags);
>  }
>  
> -static int omap_dma_slave_config(struct dma_chan *chan, struct dma_slave_config *cfg)
> +static int omap_dma_slave_config(struct dma_chan *chan,
> +				struct dma_slave_config *cfg)
>  {
>  	struct omap_chan *c = to_omap_dma_chan(chan);
>  
> -- 
> 1.9.1
> 

-- 

  parent 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
2015-05-20 20:24 ` [PATCH 1/2] dma: omap-dma: " Joe Perches
2015-05-21 15:59 ` Vinod Koul [this message]
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=20150521155934.GR3140@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