All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ashish Chavan <ashish.chavan@kpitcummins.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
	"kuninori.morimoto.gx" <kuninori.morimoto.gx@renesas.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	David@alsa-project.org, Chen <david.chen@diasemi.com>,
	lrg <lrg@ti.com>
Subject: Re: [PATCH] ASoC: da7210: Minor update for PLL and SRM
Date: Tue, 17 Apr 2012 21:00:02 +0530	[thread overview]
Message-ID: <1334676602.13279.13.camel@matrix> (raw)
In-Reply-To: <20120417145618.GL6652@opensource.wolfsonmicro.com>

On Tue, 2012-04-17 at 15:56 +0100, Mark Brown wrote:
> On Tue, Apr 17, 2012 at 08:30:58PM +0530, Ashish Chavan wrote:
> 
> > +		if ((fref == da7210_pll_div[cnt].fref) &&
> > +			(da7210->master ==  da7210_pll_div[cnt].mode) &&
> > +			(fout == da7210_pll_div[cnt].fout)) {
> 
> Since this is just a coding style thing how about lining up the (s for
> the branches?

To do that we will have to use spaces instead of tab for indentation. I
am not sure if that is fine. You mean something like below, right?

		if ((fref == da7210_pll_div[cnt].fref) &&
		    (da7210->master ==  da7210_pll_div[cnt].mode) &&
		    (fout == da7210_pll_div[cnt].fout)) {

  reply	other threads:[~2012-04-17 15:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-17 15:00 [PATCH] ASoC: da7210: Minor update for PLL and SRM Ashish Chavan
2012-04-17 14:56 ` [alsa-devel] " Mark Brown
2012-04-17 15:30   ` Ashish Chavan [this message]
2012-04-17 15:20     ` Mark Brown
2012-04-17 15:20       ` [alsa-devel] " Mark Brown

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=1334676602.13279.13.camel@matrix \
    --to=ashish.chavan@kpitcummins.com \
    --cc=David@alsa-project.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=david.chen@diasemi.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.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.