From: Mark Brown <broonie@kernel.org>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: Lyude Paul <lyude@redhat.com>, Ben Skeggs <bskeggs@redhat.com>,
Thierry Reding <thierry.reding@gmail.com>,
nouveau@lists.freedesktop.org, David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
kernel@collabora.com, Karol Herbst <kherbst@redhat.com>,
Kevin Hilman <khilman@baylibre.com>
Subject: Re: next/master boot bisection: Oops in nouveau driver on jetson-tk1
Date: Mon, 10 Dec 2018 14:25:59 +0000 [thread overview]
Message-ID: <20181210142559.GB6307@sirena.org.uk> (raw)
In-Reply-To: <16ca4f0f-6800-7204-6fc2-286caa7b850a@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
On Mon, Dec 10, 2018 at 10:00:08AM +0000, Guillaume Tucker wrote:
> On 08/12/2018 00:08, Lyude Paul wrote:
> > uhhhhhhhhhhhhh
> > didn't we fix this weeks ago? with "drm/nouveau: tegra: Call
> > nouveau_drm_device_init()"
>
> Yes here's the fix from Thierry:
>
> https://patchwork.freedesktop.org/patch/263587/
>
>
> and I can confirm that it does fix the Oops when applied on top
> of next-20181206 (what I used for the bisection last week):
>
> http://lava.baylibre.com:10080/scheduler/job/71109
>
>
> However the fix doesn't appear to have been applied in any
> upstream tree yet.
This has been broken for a considerable time now with no response from
Ben - is there some other path we can use to get the fix merged?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-12-10 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 23:31 Guillaume Tucker
2018-12-08 0:08 ` Lyude Paul
2018-12-10 10:00 ` Guillaume Tucker
2018-12-10 14:25 ` Mark Brown [this message]
2018-12-10 16:26 ` Thierry Reding
2018-12-11 0:51 ` 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=20181210142559.GB6307@sirena.org.uk \
--to=broonie@kernel.org \
--cc=airlied@linux.ie \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=guillaume.tucker@collabora.com \
--cc=kernel@collabora.com \
--cc=kherbst@redhat.com \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=nouveau@lists.freedesktop.org \
--cc=thierry.reding@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
all inboxes | Powered by JetHome®