All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Jagan Teki <jteki@openedev.com>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
	Dan Williams <dan.j.williams@intel.com>,
	Vinod Koul <vinod.koul@intel.com>
Subject: Re: [PATCH 1/2] dma: omap-dma: Fix line over 80 characters
Date: Wed, 20 May 2015 13:24:19 -0700	[thread overview]
Message-ID: <1432153459.20840.4.camel@perches.com> (raw)
In-Reply-To: <1432149070-9569-1-git-send-email-jteki@openedev.com>

On Thu, 2015-05-21 at 00:41 +0530, Jagan Teki wrote:
> This patch fixes line over 80 characters warninings while
> running checkpatch.pl

These changes aren't necessary.

If you're really going to do this, please change the style
of the functions you are using.

> diff --git 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_nochan, 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 isn't particularly human readable.

If the return type is long, it's sometimes better to
use a separate line for the return type, then put the
function on another line like:

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

> @@ -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));

This is unpleasant to read.
Just let some lines be > 80 columns.



  parent reply	other threads:[~2015-05-20 20:24 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 ` Joe Perches [this message]
2015-05-21 15:59 ` [PATCH 1/2] dma: omap-dma: " 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=1432153459.20840.4.camel@perches.com \
    --to=joe@perches.com \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=jteki@openedev.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vinod.koul@intel.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.