From: Dan Moulding <dan@danm.net>
To: dan@danm.net
Cc: airlied@redhat.com, dakr@redhat.com, kherbst@redhat.com,
lyude@redhat.com, nouveau@lists.freedesktop.org,
stable@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: [REGRESSION] v6.9-rc7: nouveau: init failed, no display output from kernel; successfully bisected
Date: Mon, 6 May 2024 12:59:10 -0600 [thread overview]
Message-ID: <20240506185910.17917-1-dan@danm.net> (raw)
In-Reply-To: <20240506182331.8076-1-dan@danm.net>
CC'ing regressions list and looping in regzbot (both of which I
accidentally left out in my initial regression report).
#regzbot introduced: 52a6947bf576
next prev parent reply other threads:[~2024-05-06 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 18:23 [REGRESSION] v6.9-rc7: nouveau: init failed, no display output from kernel; successfully bisected Dan Moulding
2024-05-06 18:59 ` Dan Moulding [this message]
2024-05-09 10:31 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-09 21:11 ` David Airlie
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=20240506185910.17917-1-dan@danm.net \
--to=dan@danm.net \
--cc=airlied@redhat.com \
--cc=dakr@redhat.com \
--cc=kherbst@redhat.com \
--cc=lyude@redhat.com \
--cc=nouveau@lists.freedesktop.org \
--cc=regressions@lists.linux.dev \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).