From: Vinod Koul <vkoul@kernel.org>
To: Bard Liao <yung-chuan.liao@linux.intel.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
pierre-louis.bossart@linux.intel.com, bard.liao@intel.com
Subject: Re: [PATCH v2 0/2] soundwire: stream: uniquify dev_err() logs
Date: Fri, 31 Mar 2023 18:45:26 +0530 [thread overview]
Message-ID: <ZCbc7omBvGNLuCcZ@matsya> (raw)
In-Reply-To: <20230322035524.1509029-1-yung-chuan.liao@linux.intel.com>
On 22-03-23, 11:55, Bard Liao wrote:
> There are a couple of duplicate logs which makes harder than needed to
> follow the error flows. Add __func__ or make the log unique.
> This series also changed some uses of "dev_err(bus->dev," where the stream
> may depend on multiple managers/buses.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2023-03-31 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 3:55 [PATCH v2 0/2] soundwire: stream: uniquify dev_err() logs Bard Liao
2023-03-22 3:55 ` [PATCH v2 1/2] soundwire: stream: remove bus->dev from logs on multiple buses Bard Liao
2023-03-22 3:55 ` [PATCH v2 2/2] soundwire: stream: uniquify dev_err() logs Bard Liao
2023-03-31 13:15 ` Vinod Koul [this message]
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=ZCbc7omBvGNLuCcZ@matsya \
--to=vkoul@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=yung-chuan.liao@linux.intel.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