From: Bard Liao <yung-chuan.liao@linux.intel.com>
To: alsa-devel@alsa-project.org, vkoul@kernel.org
Cc: vinod.koul@linaro.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org, srinivas.kandagatla@linaro.org,
rander.wang@linux.intel.com, hui.wang@canonical.com,
pierre-louis.bossart@linux.intel.com, sanyog.r.kale@intel.com,
bard.liao@intel.com
Subject: [PATCH 0/5] soundwire: add missing \n in dev_err()
Date: Tue, 23 Mar 2021 08:58:50 +0800 [thread overview]
Message-ID: <20210323005855.20890-1-yung-chuan.liao@linux.intel.com> (raw)
We fixed a lot of warnings in 2019 but the magic of copy-paste keeps
adding new ones...
Pierre-Louis Bossart (5):
soundwire: intel: add missing \n in dev_err()
soundwire: bandwidth_allocation: add missing \n in dev_err()
soundwire: cadence: add missing \n in dev_err()
soundwire: stream: add missing \n in dev_err()
soundwire: qcom: add missing \n in dev_err()
drivers/soundwire/cadence_master.c | 2 +-
.../soundwire/generic_bandwidth_allocation.c | 4 ++--
drivers/soundwire/intel.c | 18 +++++++++---------
drivers/soundwire/qcom.c | 2 +-
drivers/soundwire/stream.c | 10 +++++-----
5 files changed, 18 insertions(+), 18 deletions(-)
--
2.17.1
next reply other threads:[~2021-03-23 0:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 0:58 Bard Liao [this message]
2021-03-23 0:58 ` [PATCH 1/5] soundwire: intel: " Bard Liao
2021-03-23 0:58 ` [PATCH 2/5] soundwire: bandwidth_allocation: " Bard Liao
2021-03-23 0:58 ` [PATCH 3/5] soundwire: cadence: " Bard Liao
2021-03-23 0:58 ` [PATCH 4/5] soundwire: stream: " Bard Liao
2021-03-23 0:58 ` [PATCH 5/5] soundwire: qcom: " Bard Liao
2021-03-23 6:50 ` [PATCH 0/5] soundwire: " Vinod Koul
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=20210323005855.20890-1-yung-chuan.liao@linux.intel.com \
--to=yung-chuan.liao@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hui.wang@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rander.wang@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=vinod.koul@linaro.org \
--cc=vkoul@kernel.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 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®