From: Mark Brown <broonie@kernel.org>
To: John Stultz <john.stultz@linaro.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Patrick Lai <plai@codeaurora.org>,
Banajit Goswami <bgoswami@codeaurora.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Vinod Koul <vkoul@kernel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Stephan Gerhold <stephan@gerhold.net>,
Sami Tolvanen <samitolvanen@google.com>,
Todd Kjos <tkjos@google.com>, Alistair Delva <adelva@google.com>,
Amit Pundir <amit.pundir@linaro.org>,
Sumit Semwal <sumit.semwal@linaro.org>,
alsa-devel@alsa-project.org
Subject: Re: [RFC][PATCH] ASoC: qcom: q6asm-dai: kCFI fix
Date: Mon, 1 Jun 2020 11:49:44 +0100 [thread overview]
Message-ID: <20200601104944.GA5234@sirena.org.uk> (raw)
In-Reply-To: <20200529213823.98812-1-john.stultz@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
On Fri, May 29, 2020 at 09:38:23PM +0000, John Stultz wrote:
> [ 82.585661] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000001
> [ 82.595387] Mem abort info:
> [ 82.599463] ESR = 0x96000005
> [ 82.602658] EC = 0x25: DABT (current EL), IL = 32 bits
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 --]
next prev parent reply other threads:[~2020-06-01 10:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 21:38 John Stultz
2020-06-01 9:33 ` Srinivas Kandagatla
2020-06-01 10:49 ` Mark Brown [this message]
2020-06-01 11:53 ` [PATCH] " Mark Brown
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=20200601104944.GA5234@sirena.org.uk \
--to=broonie@kernel.org \
--cc=adelva@google.com \
--cc=alsa-devel@alsa-project.org \
--cc=amit.pundir@linaro.org \
--cc=bgoswami@codeaurora.org \
--cc=john.stultz@linaro.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=plai@codeaurora.org \
--cc=samitolvanen@google.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=stephan@gerhold.net \
--cc=sumit.semwal@linaro.org \
--cc=tiwai@suse.com \
--cc=tkjos@google.com \
--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®