From: Mark Brown <broonie@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Robin Murphy <robin.murphy@arm.com>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Arnd Bergmann <arnd@arndb.de>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
John Stultz <john.stultz@linaro.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: Linux-next-20191106 : arm64: Internal error: Oops: 96000007
Date: Thu, 7 Nov 2019 11:45:53 +0000 [thread overview]
Message-ID: <20191107114553.GA6159@sirena.co.uk> (raw)
In-Reply-To: <CACRpkdY5JObOobs7VW043QYGd_xufwnQDBJseKp+_QWv4kdzaQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 526 bytes --]
On Thu, Nov 07, 2019 at 09:00:25AM +0100, Linus Walleij wrote:
> I wonder if it's worth to look at the static checkers like checkpatch
> to warn for this?
I noticed this due to the warning emitted in the build process so I'm
not sure there'd be much more chance that people would notice (though
admittedly the warning during the build doesn't suggest a boot problem).
There's hundreds of other examples in the tree that don't trigger
crashes for whatever reason, I think this one was just noticable because
it got built in.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-11-07 11:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 15:56 Linux-next-20191106 : arm64: Internal error: Oops: 96000007 Naresh Kamboju
2019-11-06 16:07 ` Robin Murphy
2019-11-06 16:16 ` Mark Rutland
2019-11-06 16:17 ` Mark Brown
2019-11-07 8:00 ` Linus Walleij
2019-11-07 11:45 ` Mark Brown [this message]
2019-11-07 11:59 ` Ben Dooks
2019-11-06 17:19 ` Russell King - ARM Linux admin
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=20191107114553.GA6159@sirena.co.uk \
--to=broonie@kernel.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=john.stultz@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=robin.murphy@arm.com \
--cc=sfr@canb.auug.org.au \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).