From: Zhang Han <zhanghan64@huawei.com>
To: <kraxel@redhat.com>
Cc: hunongda@huawei.com, zhang.zhanghailiang@huawei.com,
qemu-trivial@nongnu.org, qemu-devel@nongnu.org,
alex.chen@huawei.com, zhanghan64@huawei.com
Subject: [PATCH 0/6] Fix some style problems in audio
Date: Thu, 14 Jan 2021 16:10:53 +0800 [thread overview]
Message-ID: <20210114081059.19632-1-zhanghan64@huawei.com> (raw)
Some style problems in audio directory are found by checkpatch.pl. Fix these
style problems.
Zhang Han (6):
audio: Add braces for statements/fix braces' position
audio: Add spaces around operator/delete redundant spaces
audio: foo* bar" should be "foo *bar".
audio: Fix lines over 90 characters
audio: Don't use '#' flag of printf format ('%#') in format strings
audio: Suspect code indent for conditional statements
audio/alsaaudio.c | 15 +++++--------
audio/audio.c | 26 ++++++++++------------
audio/audio_template.h | 14 +++++-------
audio/coreaudio.c | 17 +++++++-------
audio/dsoundaudio.c | 50 +++++++++++++++++++++++++++---------------
audio/jackaudio.c | 2 +-
audio/ossaudio.c | 12 ++++------
audio/paaudio.c | 2 +-
8 files changed, 68 insertions(+), 70 deletions(-)
--
2.29.1.59.gf9b6481aed
next reply other threads:[~2021-01-14 8:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 8:10 Zhang Han [this message]
2021-01-14 8:10 ` [PATCH 1/6] audio: Add braces for statements/fix braces' position Zhang Han
2021-01-14 8:10 ` [PATCH 2/6] audio: Add spaces around operator/delete redundant spaces Zhang Han
2021-01-14 8:10 ` [PATCH 3/6] audio: foo* bar" should be "foo *bar" Zhang Han
2021-01-14 8:10 ` [PATCH 4/6] audio: Fix lines over 90 characters Zhang Han
2021-01-14 8:10 ` [PATCH 5/6] audio: Don't use '#' flag of printf format ('%#') in Zhang Han
2021-01-14 8:10 ` [PATCH 6/6] audio: Suspect code indent for conditional statements Zhang Han
2021-01-14 8:40 ` [PATCH 0/6] Fix some style problems in audio no-reply
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=20210114081059.19632-1-zhanghan64@huawei.com \
--to=zhanghan64@huawei.com \
--cc=alex.chen@huawei.com \
--cc=hunongda@huawei.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=zhang.zhanghailiang@huawei.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 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.