From: Mark Brown <broonie@kernel.org>
To: Yassine Oudjana <yassine.oudjana@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Aidan MacDonald <aidanmacdonald.0x0@gmail.com>,
linux-kernel@vger.kernel.org,
Yassine Oudjana <y.oudjana@protonmail.com>
Subject: Re: [PATCH] regmap-irq: Use the new num_config_regs property in regmap_add_irq_chip_fwnode
Date: Wed, 9 Nov 2022 18:31:25 +0000 [thread overview]
Message-ID: <Y2vx/WwCwWhay+W+@sirena.org.uk> (raw)
In-Reply-To: <20221107202114.823975-1-y.oudjana@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 755 bytes --]
On Mon, Nov 07, 2022 at 11:21:14PM +0300, Yassine Oudjana wrote:
> [ 39.199374] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
> [ 39.199383] Mem abort info:
> [ 39.199390] ESR = 0x0000000096000004
> [ 39.199397] EC = 0x25: DABT (current EL), IL = 32 bits
> [ 39.199408] SET = 0, FnV = 0
> [ 39.199415] EA = 0, S1PTW = 0
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:[~2022-11-09 18:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 20:21 [PATCH] regmap-irq: Use the new num_config_regs property in regmap_add_irq_chip_fwnode Yassine Oudjana
2022-11-07 23:58 ` Aidan MacDonald
2022-11-09 18:31 ` Mark Brown [this message]
2022-11-10 21:13 ` Mark Brown
2022-11-12 13:52 ` Aidan MacDonald
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=Y2vx/WwCwWhay+W+@sirena.org.uk \
--to=broonie@kernel.org \
--cc=aidanmacdonald.0x0@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=y.oudjana@protonmail.com \
--cc=yassine.oudjana@gmail.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