From: Mark Brown <broonie@kernel.org>
To: Judy Hsiao <judyhsiao@chromium.org>
Cc: judyhsiao@google.com, Banajit Goswami <bgoswami@codeaurora.org>,
cychiang@google.com, alsa-devel@alsa-project.org,
Liam Girdwood <lgirdwood@gmail.com>,
linux-arm-msm@vger.kernel.org, swboyd@chromium.org,
dianders@chromium.org, Takashi Iwai <tiwai@suse.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
yuhsuan@chromium.org
Subject: Re: [v2] SoC: qcom: Distinguish headset codec by codec_dai->name
Date: Mon, 13 Dec 2021 16:06:26 +0000 [thread overview]
Message-ID: <YbdvgsxMThr0e8zl@sirena.org.uk> (raw)
In-Reply-To: <20211213023626.673323-1-judyhsiao@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 566 bytes --]
On Mon, Dec 13, 2021 at 10:36:26AM +0800, Judy Hsiao wrote:
> Call stack of the crash:
> ```
> Unable to handle kernel paging request at virtual address ffffffbfe7bba9ce
> Mem abort info:
Please think hard before including complete backtraces in upstream
reports, they are very large and contain almost no useful information
relative to their size so often obscure the relevant content in your
message. If part of the backtrace is usefully illustrative (it often is
for search engines if nothing else) then it's usually better to pull out
the relevant sections.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-12-13 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 2:36 [v2] SoC: qcom: Distinguish headset codec by codec_dai->name Judy Hsiao
2021-12-13 16:06 ` Mark Brown [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=YbdvgsxMThr0e8zl@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@codeaurora.org \
--cc=cychiang@google.com \
--cc=dianders@chromium.org \
--cc=judyhsiao@chromium.org \
--cc=judyhsiao@google.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=swboyd@chromium.org \
--cc=tiwai@suse.com \
--cc=yuhsuan@chromium.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;
as well as URLs for NNTP newsgroup(s).