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 0/5] staging: bcm2835-audio: fix multiple checkpatch issues in bcm2835-vchiq.c
Date: Fri, 3 Mar 2017 23:46:30 +0530	[thread overview]
Message-ID: <cover.1488564925.git.aishpant@gmail.com> (raw)

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

Aishwarya Pant (5):

  staging-audio: remove spaces after cast
  staging: bcm2835-audio: use braces on all arms of statement
  staging: bcm2835-audio: fix typo in word
  staging: bcm2835-audio: match alignment with open parenthesis
  staging: bcm2835-audio: use min_t() macro instead of min()

 .../vc04_services/bcm2835-audio/bcm2835-vchiq.c    | 34 ++++++++++++----------
 1 file changed, 18 insertions(+), 16 deletions(-)

-- 
2.7.4



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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03 18:16 Aishwarya Pant [this message]
2017-03-03 18:16 ` [PATCH 1/5] staging: bcm2835-audio: remove spaces after cast Aishwarya Pant
2017-03-03 18:17 ` [PATCH 2/5] staging: bcm2835-audio: use braces on all arms of statement Aishwarya Pant
2017-03-03 18:17 ` [PATCH 3/5] staging: bcm2835-audio: fix typo in word Aishwarya Pant
2017-03-03 18:17 ` [PATCH 4/5] staging: bcm2835-audio: match alignment with open parenthesis Aishwarya Pant
2017-03-03 18:20 ` [PATCH 5/5] staging: bcm2835-audio: use min_t() macro instead of min() Aishwarya Pant

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.1488564925.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.