All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aishwarya Pant <aishpant@gmail.com>
To: Stephen Warren <swarren@wwwdotorg.org>,
	Lee Jones <lee@kernel.org>, Eric Anholt <eric@anholt.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Ray Jui <rjui@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>,
	bcm-kernel-feedback-list@broadcom.com
Cc: outreachy-kernel@googlegroups.com
Subject: [PATCH v4 0/5] staging: bcm2835-audio: fix multiple checkpatch warnings
Date: Fri, 3 Mar 2017 00:14:29 +0530	[thread overview]
Message-ID: <cover.1488479861.git.aishpant@gmail.com> (raw)

Fix multiple code styling warnings issued by checkpatch on file 
bcm2835-ctl.c in bcm2835-audio driver 


Changes in v4:
	-Refactor commit messages
Changes in v3: 
	-Merge two if conditions 
	-Fix subject of patch replace printk(... by dev_err(... 
Changes in v2: 
	-Replace pr_err with dev_err

Aishwarya Pant (5):
*** HERE ***
  staging: bcm2835-audio: remove space after cast
  staging: bcm2835-audio: move logical continuation to the same line
  staging: bcm2835-audio: use kernel preferred block commenting style
  staging: bcm2835-audio: remove extra blank line
  staging: bcm2835-audio: replace printk(KERN_ERR...) with dev_err(...)

 .../vc04_services/bcm2835-audio/bcm2835-ctl.c      | 23 ++++++++++------------
 1 file changed, 10 insertions(+), 13 deletions(-)

-- 
2.7.4



             reply	other threads:[~2017-03-02 18:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-02 18:44 Aishwarya Pant [this message]
2017-03-02 18:45 ` [PATCH v4 1/5] staging: bcm2835-audio: move logical continuation to the same line Aishwarya Pant
2017-03-02 22:43   ` [Outreachy kernel] " Julia Lawall
2017-03-02 22:43     ` Julia Lawall

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=cover.1488479861.git.aishpant@gmail.com \
    --to=aishpant@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=eric@anholt.net \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=lee@kernel.org \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=rjui@broadcom.com \
    --cc=sbranden@broadcom.com \
    --cc=swarren@wwwdotorg.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.