public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: wei_wang@realsil.com.cn
Cc: cjb@laptop.org, sameo@linux.intel.com,
	devel@linuxdriverproject.org, linux-kernel@vger.kernel.org,
	linux-mmc@vger.kernel.org, gregkh@linuxfoundation.org,
	arnd@arndb.de, oakad@yahoo.com
Subject: Re: [PATCH 7/7] MFD:rtsx: Fix checkpatch warning
Date: Mon, 24 Dec 2012 17:10:25 +0100	[thread overview]
Message-ID: <20121224161025.GF6702@liondog.tnic> (raw)
In-Reply-To: <fd3b65dc90ea95d4e904885fe8eefff295450f2a.1356319097.git.wei_wang@realsil.com.cn>

On Mon, Dec 24, 2012 at 02:03:56PM +0800, wei_wang@realsil.com.cn wrote:
> From: Wei WANG <wei_wang@realsil.com.cn>
> 
> WARNING: Avoid CamelCase: <min_N>
> +	u8 N, min_N, max_N, clk_divider;
> 
> WARNING: Avoid CamelCase: <max_N>
> +	u8 N, min_N, max_N, clk_divider;
> 
> Signed-off-by: Wei WANG <wei_wang@realsil.com.cn>
> ---
>  drivers/mfd/rtsx_pcr.c |   26 +++++++++++++-------------
>  1 file changed, 13 insertions(+), 13 deletions(-)
> 
> diff --git a/drivers/mfd/rtsx_pcr.c b/drivers/mfd/rtsx_pcr.c
> index cc28f17..f843c73 100644
> --- a/drivers/mfd/rtsx_pcr.c
> +++ b/drivers/mfd/rtsx_pcr.c
> @@ -590,7 +590,7 @@ int rtsx_pci_switch_clock(struct rtsx_pcr *pcr, unsigned int card_clock,
>  		u8 ssc_depth, bool initial_mode, bool double_clk, bool vpclk)
>  {
>  	int err, clk;
> -	u8 N, min_N, max_N, clk_divider;
> +	u8 n, min_n, max_n, clk_divider;
>  	u8 mcu_cnt, div, max_div;
>  	u8 depth[] = {
>  		[RTSX_SSC_DEPTH_4M] = SSC_DEPTH_4M,
> @@ -615,8 +615,8 @@ int rtsx_pci_switch_clock(struct rtsx_pcr *pcr, unsigned int card_clock,
>  	card_clock /= 1000000;
>  	dev_dbg(&(pcr->pci->dev), "Switch card clock to %dMHz\n", card_clock);
>  
> -	min_N = 80;
> -	max_N = 208;
> +	min_n = 80;
> +	max_n = 208;

Naked magic values? Maybe macro defines with descriptive names instead?

Thanks.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

      reply	other threads:[~2012-12-24 16:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-24  6:03 [PATCH 0/7] rtsx patchset for MFD and MMC tree wei_wang
2012-12-24  6:03 ` [PATCH 1/7] MFD:rtsx: Fix typo in comment wei_wang
2012-12-24  6:03 ` [PATCH 2/7] MFD:rtsx: Remove redundant code wei_wang
2012-12-24 10:11   ` Borislav Petkov
2012-12-24  6:03 ` [PATCH 3/7] MFD:rtsx: Declare that the DMA address limitation is 32bit explicitly wei_wang
2012-12-24 13:08   ` Borislav Petkov
2012-12-24  6:03 ` [PATCH 4/7] MFD:rtsx: Add callback function switch_output_voltage wei_wang
2012-12-24  6:03 ` [PATCH 5/7] MMC:rtsx: Using callback function to switch output voltage wei_wang
2012-12-24  6:03 ` [PATCH 6/7] MFD:rtsx: Add callback function conv_clk_and_div_n wei_wang
2012-12-24  6:03 ` [PATCH 7/7] MFD:rtsx: Fix checkpatch warning wei_wang
2012-12-24 16:10   ` Borislav Petkov [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=20121224161025.GF6702@liondog.tnic \
    --to=bp@alien8.de \
    --cc=arnd@arndb.de \
    --cc=cjb@laptop.org \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=oakad@yahoo.com \
    --cc=sameo@linux.intel.com \
    --cc=wei_wang@realsil.com.cn \
    /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