From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: David Airlie <airlied-cv59FeDIM0c@public.gmane.org>,
Guillaume Tucker
<guillaume.tucker-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
Ben Skeggs <bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
kernel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org,
Kevin Hilman <khilman-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
Subject: Re: next/master boot bisection: Oops in nouveau driver on jetson-tk1
Date: Tue, 11 Dec 2018 00:51:28 +0000 [thread overview]
Message-ID: <20181211005128.GA3004@sirena.org.uk> (raw)
In-Reply-To: <20181210162622.GB4789@ulmo>
[-- Attachment #1.1: Type: text/plain, Size: 588 bytes --]
On Mon, Dec 10, 2018 at 05:26:22PM +0100, Thierry Reding wrote:
> On Mon, Dec 10, 2018 at 02:25:59PM +0000, Mark Brown wrote:
> > 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?
> I suppose we could go directly via Dave. But Ben's usually pretty
> responsive, so he probably just missed it. Let me ping him on IRC, maybe
> that'll get his attention.
This is at least the third go at reporting this as a boot failure IIRC
so these clearly aren't doing the trick :/ . Perhaps a resend as well?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
prev parent reply other threads:[~2018-12-11 0:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 23:31 next/master boot bisection: Oops in nouveau driver on jetson-tk1 Guillaume Tucker
[not found] ` <89fa50d0-945f-d1ed-ae55-ee947187f209-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2018-12-08 0:08 ` Lyude Paul
2018-12-10 10:00 ` Guillaume Tucker
[not found] ` <16ca4f0f-6800-7204-6fc2-286caa7b850a-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2018-12-10 14:25 ` Mark Brown
[not found] ` <20181210142559.GB6307-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2018-12-10 16:26 ` Thierry Reding
2018-12-11 0:51 ` 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=20181211005128.GA3004@sirena.org.uk \
--to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=airlied-cv59FeDIM0c@public.gmane.org \
--cc=bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=guillaume.tucker-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org \
--cc=kernel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org \
--cc=khilman-rdvid1DuHRBWk0Htik3J/w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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