All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Hongbo Zhang <hongbo.zhang@freescale.com>
Cc: vkoul@infradead.org, dan.j.williams@intel.com,
	dmaengine@vger.kernel.org, scottwood@freescale.com,
	leo.li@freescale.com, linuxppc-dev@lists.ozlabs.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 6/8] DMA: Freescale: change descriptor release process for supporting async_tx
Date: Mon, 14 Apr 2014 16:41:57 +0300	[thread overview]
Message-ID: <1397482917.11914.128.camel@smile.fi.intel.com> (raw)
In-Reply-To: <5347A8F2.4050603@freescale.com>

On Fri, 2014-04-11 at 16:33 +0800, Hongbo Zhang wrote:

> >>> +         * hardware channel, subsequent descriptors are either in
> >>> +         * process or have not been submitted
> >> Dot at the eol. Check in all comments.
> >
> > Even though I saw there are other comments without the dots, I think 
> > it is better to have it.
> > Thanks, all.
> >
> Hmm... think it again, it it really necessary to have it?
> Even I have it in my patch, there are already so many comments exists 
> without it.

For my opinion is better to keep style in your patches. Better if it
commonly used style in the driver. But comment against comments is
really minor thing.

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy


WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Hongbo Zhang <hongbo.zhang@freescale.com>
Cc: leo.li@freescale.com, vkoul@infradead.org,
	linux-kernel@vger.kernel.org, scottwood@freescale.com,
	dmaengine@vger.kernel.org, dan.j.williams@intel.com,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3 6/8] DMA: Freescale: change descriptor release process for supporting async_tx
Date: Mon, 14 Apr 2014 16:41:57 +0300	[thread overview]
Message-ID: <1397482917.11914.128.camel@smile.fi.intel.com> (raw)
In-Reply-To: <5347A8F2.4050603@freescale.com>

On Fri, 2014-04-11 at 16:33 +0800, Hongbo Zhang wrote:

> >>> +         * hardware channel, subsequent descriptors are either in
> >>> +         * process or have not been submitted
> >> Dot at the eol. Check in all comments.
> >
> > Even though I saw there are other comments without the dots, I think 
> > it is better to have it.
> > Thanks, all.
> >
> Hmm... think it again, it it really necessary to have it?
> Even I have it in my patch, there are already so many comments exists 
> without it.

For my opinion is better to keep style in your patches. Better if it
commonly used style in the driver. But comment against comments is
really minor thing.

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

  reply	other threads:[~2014-04-14 13:42 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10  7:09 [PATCH v3 0/8] DMA: Freescale: driver cleanups and enhancements hongbo.zhang
2014-04-10  7:09 ` hongbo.zhang
2014-04-10  7:09 ` [PATCH v3 1/8] DMA: Freescale: remove the unnecessary FSL_DMA_LD_DEBUG hongbo.zhang
2014-04-10  7:09   ` hongbo.zhang
2014-04-10  7:20   ` [PATCH v3 0/8] DMA: Freescale: driver cleanups and enhancements Hongbo Zhang
2014-04-10  7:20     ` Hongbo Zhang
2014-04-10  7:09 ` [PATCH v3 2/8] DMA: Freescale: unify register access methods hongbo.zhang
2014-04-10  7:09   ` hongbo.zhang
2014-04-10  8:46   ` David Laight
2014-04-10  8:46     ` David Laight
2014-04-10  9:33     ` Hongbo Zhang
2014-04-10  7:10 ` [PATCH v3 3/8] DMA: Freescale: remove attribute DMA_INTERRUPT of dmaengine hongbo.zhang
2014-04-10  7:10   ` hongbo.zhang
2014-04-10  7:10 ` [PATCH v3 4/8] DMA: Freescale: add fsl_dma_free_descriptor() to reduce code duplication hongbo.zhang
2014-04-10  7:10   ` hongbo.zhang
2014-04-10 11:29   ` Andy Shevchenko
2014-04-10 11:29     ` Andy Shevchenko
2014-04-11  8:14     ` Hongbo Zhang
2014-04-11  8:14       ` Hongbo Zhang
2014-04-14 13:40       ` Andy Shevchenko
2014-04-14 13:40         ` Andy Shevchenko
2014-04-18  4:09         ` Hongbo Zhang
2014-04-18  4:09           ` Hongbo Zhang
2014-04-10  7:10 ` [PATCH v3 5/8] DMA: Freescale: move functions to avoid forward declarations hongbo.zhang
2014-04-10  7:10   ` hongbo.zhang
2014-04-10  7:10 ` [PATCH v3 6/8] DMA: Freescale: change descriptor release process for supporting async_tx hongbo.zhang
2014-04-10  7:10   ` hongbo.zhang
2014-04-10 11:56   ` Andy Shevchenko
2014-04-10 11:56     ` Andy Shevchenko
2014-04-11  8:00     ` Hongbo Zhang
2014-04-11  8:00       ` Hongbo Zhang
2014-04-11  8:33       ` Hongbo Zhang
2014-04-11  8:33         ` Hongbo Zhang
2014-04-14 13:41         ` Andy Shevchenko [this message]
2014-04-14 13:41           ` Andy Shevchenko
2014-04-10  7:10 ` [PATCH v3 7/8] DMA: Freescale: use spin_lock_bh instead of spin_lock_irqsave hongbo.zhang
2014-04-10  7:10   ` hongbo.zhang
2014-04-10  7:10 ` [PATCH v3 8/8] DMA: Freescale: add suspend resume functions for DMA driver hongbo.zhang
2014-04-10  7:10   ` hongbo.zhang
2014-04-10 12:05   ` Andy Shevchenko
2014-04-10 12:05     ` Andy Shevchenko
2014-04-11  7:42     ` Hongbo Zhang
2014-04-11  7:42       ` Hongbo Zhang

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=1397482917.11914.128.camel@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=hongbo.zhang@freescale.com \
    --cc=leo.li@freescale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=scottwood@freescale.com \
    --cc=vkoul@infradead.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 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.