mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: ShaRab Shaik <sharab.shaik@gmail.com>
Cc: perex@perex.cz, tiwai@suse.de, alsa-devel@alsa-project.org,
	linux-kernel@vger.kernel.org, lgirdwood@gmail.com
Subject: Re: [PATCH] sound: tlv320aic32x4: Fixed Coding style issues
Date: Wed, 4 Jun 2014 13:42:24 +0100	[thread overview]
Message-ID: <20140604124224.GK2520@sirena.org.uk> (raw)
In-Reply-To: <CAHWZSxgM17azkvwxOAcR3skaUXRcaoxbiHxE3bMNrfg2dNTRkw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1373 bytes --]

On Wed, Jun 04, 2014 at 04:49:54PM +0530, ShaRab Shaik wrote:
> From 617d7a25f3c0c08e0b95b24de2d1ea0f3f4b98c7 Mon Sep 17 00:00:00 2001
> From: Shahina Shaik <sharab.shaik@gmail.com>
> Date: Wed, 4 Jun 2014 16:27:19 +0530
> Subject: [PATCH] sound: tlv320aic32x4: Fixed Coding style issues.
> 
> Fixed brace coding style, lines morethan 80 characters issues.

Your patch appears to have been corrupted by your mailer, it's word
wrapped so can't be applied by the tools.  Please see
Documentation/SubmittingPatches and Documentation/email-clients.txt for
some suggestions on how to set this up.

> Replaced printk with pr_err as pr_err is prefered than printk.

In general dev_err() is going to be usable by CODEC drivers and is even
more strongly preferred than pr_err() since it provides more information
about the source of the error.

Please also avoid making multiple kinds of change in the same patch - it
is much easier to review things if the patch is simpler.

> -    if (aic32x4->power_cfg & AIC32X4_PWR_AVDD_DVDD_WEAK_DISABLE) {
> +    if (aic32x4->power_cfg & AIC32X4_PWR_AVDD_DVDD_WEAK_DISABLE)
>          snd_soc_write(codec, AIC32X4_PWRCFG, AIC32X4_AVDDWEAKDISABLE);
> -    }
> +

So for example the print changes should be a separate patch to these
brace  changes.  If you're removing the } you should also just delete
the line.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

           reply	other threads:[~2014-06-04 12:42 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAHWZSxgM17azkvwxOAcR3skaUXRcaoxbiHxE3bMNrfg2dNTRkw@mail.gmail.com>]

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=20140604124224.GK2520@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=sharab.shaik@gmail.com \
    --cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®