From: Mark Brown <broonie@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Siddharth Kapoor <ksiddharth@google.com>,
lee.jones@linaro.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: Kernel panic on Google Pixel devices due to regulator patch
Date: Wed, 18 Dec 2019 17:03:04 +0000 [thread overview]
Message-ID: <20191218170304.GI3219@sirena.org.uk> (raw)
In-Reply-To: <20191218162424.GA482612@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
On Wed, Dec 18, 2019 at 05:24:24PM +0100, Greg KH wrote:
> On Wed, Dec 18, 2019 at 04:18:06PM +0000, Mark Brown wrote:
> > What you appear to have caught here is an interaction with some
> > unreviewed vendor code - how much of that is going on in the vendor
> > trees you're not testing? If we want to encourage people to pull in
> > stable we should be paying attention to that sort of stuff.
> I get weekly merge reports from all of the major SoC vendors when they
> pull these releases into their tree and run through their full suite of
> tests. So I am paying attention to this type of thing.
Are you sure you're not just definining major SoC vendors as being
people who send you reports here? :P In any case, that's only going to
cover a limited subset of potential drivers and subsystems, devices that
don't appear on reference designs aren't going to get any coverage at
all that way for example.
> What I need to figure out here is what is going wrong and why the SoC's
> testing did not catch this. That's going to take a bit longer...
There's a reasonable chance this is something board specific.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-12-18 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJRo92+eD9F6Q60yVY2PfwaPWO_8Dts8QwH7mhpJaem7SpLihg@mail.gmail.com>
2019-12-18 11:34 ` Kernel panic on Google Pixel devices due to regulator patch Mark Brown
2019-12-18 12:21 ` Greg KH
2019-12-18 13:11 ` Mark Brown
2019-12-18 14:22 ` Greg KH
2019-12-18 16:18 ` Mark Brown
2019-12-18 16:24 ` Greg KH
2019-12-18 17:03 ` 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=20191218170304.GI3219@sirena.org.uk \
--to=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=ksiddharth@google.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.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).