From: Adrien Thierry <athierry@redhat.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
Maxime Ripard <mripard@kernel.org>, Takashi Iwai <tiwai@suse.com>
Cc: linux-staging@lists.linux.dev,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Adrien Thierry <athierry@redhat.com>
Subject: [PATCH 0/2] staging: bcm2835-audio: minor code style cleanups
Date: Thu, 14 Apr 2022 11:23:38 -0400 [thread overview]
Message-ID: <20220414152340.68932-1-athierry@redhat.com> (raw)
This series contains minor code style cleanups to fix checkpatch warnings.
This handles TODO item "Fix the remaining checkpatch.pl errors and
warnings"
Adrien Thierry (2):
staging: bcm2835-audio: fully describe config symbol
staging: bcm2835-audio: clean code style warnings
drivers/staging/vc04_services/bcm2835-audio/Kconfig | 5 ++++-
drivers/staging/vc04_services/bcm2835-audio/bcm2835-pcm.c | 5 ++---
drivers/staging/vc04_services/bcm2835-audio/bcm2835-vchiq.c | 2 +-
drivers/staging/vc04_services/bcm2835-audio/bcm2835.h | 2 +-
4 files changed, 8 insertions(+), 6 deletions(-)
base-commit: 194193dd06848c1839d928090cb2032eec8b2f9c
--
2.35.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-04-14 15:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 15:23 Adrien Thierry [this message]
2022-04-14 15:23 ` [PATCH 1/2] staging: bcm2835-audio: fully describe config symbol Adrien Thierry
2022-04-14 16:21 ` Greg Kroah-Hartman
2022-04-14 15:23 ` [PATCH 2/2] staging: bcm2835-audio: clean code style warnings Adrien Thierry
2022-04-14 16:20 ` Greg Kroah-Hartman
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=20220414152340.68932-1-athierry@redhat.com \
--to=athierry@redhat.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-staging@lists.linux.dev \
--cc=mripard@kernel.org \
--cc=nsaenz@kernel.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=tiwai@suse.com \
/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;
as well as URLs for NNTP newsgroup(s).