All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Prameela Rani Garnepudi <prameela.j04cs@gmail.com>
Cc: linux-wireless@vger.kernel.org, johannes.berg@intel.com,
	hofrat@osadl.org, xypron.glpk@gmx.de,
	prameela.garnepudi@redpinesignals.com
Subject: Re: [PATCH] rsi: update in boot parameters
Date: Wed, 12 Oct 2016 17:37:57 +0300	[thread overview]
Message-ID: <87fuo1eipm.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1475660148-14087-1-git-send-email-prameela.j04cs@gmail.com> (Prameela Rani Garnepudi's message of "Wed, 5 Oct 2016 15:05:48 +0530")

Prameela Rani Garnepudi <prameela.j04cs@gmail.com> writes:

> Added more clock switch fields in boot parameters configured to device
>
> Signed-off-by: Prameela Rani Garnepudi <prameela.j04cs@gmail.com>

Why? How does this help?

>  			.tapll_info_g = {
> -				.pll_reg_1 = cpu_to_le16((TA_PLL_N_VAL_20 << 8)|
> -					      (TA_PLL_M_VAL_20)),
> -				.pll_reg_2 = cpu_to_le16(TA_PLL_P_VAL_20),
> +				.pll_reg_1 = cpu_to_le16((TAPLL_N_VAL_20 << 8) |
> +							 (TAPLL_M_VAL_20)),
> +				.pll_reg_2 = cpu_to_le16(TAPLL_P_VAL_20),

Doing changes from TA_PLL_N_VAL_20 to TAPLL_N_VAL_20 makes this hard to
review. Only one logical change per patch, please. And make style
changes separately from functional changes.

>  			},
>  			.pll960_info_g = {
> -				.pll_reg_1 = cpu_to_le16((PLL960_P_VAL_20 << 8)|
> +				.pll_reg_1 = cpu_to_le16((PLL960_P_VAL_20 << 8) |

Again unnecessary style change.

> -#define TA_PLL_M_VAL_20                  8
> -#define TA_PLL_N_VAL_20                  1
> -#define TA_PLL_P_VAL_20                  4
> +#define TAPLL_M_VAL_20			8
> +#define TAPLL_N_VAL_20			1
> +#define TAPLL_P_VAL_20			4

I don't really see the point with the rename. Changing the spaces to
tabs I understand, though.

But now that you are just starting don't waste time doing code style
changes, instead focus on fixing functionality or adding new features.
The style changes can be done later when you are more familiar with
everything.

I stopped now, please resend without the style changes so that it's
easier to review.

-- 
Kalle Valo

      reply	other threads:[~2016-10-12 14:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-05  9:35 [PATCH] rsi: update in boot parameters Prameela Rani Garnepudi
2016-10-12 14:37 ` Kalle Valo [this message]

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=87fuo1eipm.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=hofrat@osadl.org \
    --cc=johannes.berg@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=prameela.garnepudi@redpinesignals.com \
    --cc=prameela.j04cs@gmail.com \
    --cc=xypron.glpk@gmx.de \
    /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.