From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Thomas Backlund <tmb@mageia.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Sven Joachim <svenjoac@gmx.de>, stable <stable@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dave Airlie <airlied@redhat.com>
Subject: Re: Linux 5.1.9 build failure with CONFIG_NOUVEAU_LEGACY_CTX_SUPPORT=n
Date: Sat, 15 Jun 2019 17:27:59 +0200 [thread overview]
Message-ID: <20190615152759.GA5171@kroah.com> (raw)
In-Reply-To: <7c9602d9-0619-2a01-5793-dbcf259d10df@mageia.org>
On Sat, Jun 15, 2019 at 01:21:59PM +0300, Thomas Backlund wrote:
> Den 13-06-2019 kl. 10:42, skrev Greg Kroah-Hartman:
>
> > I've just reverted it now.
> >
> > If someone can send me a patch series of all of what needs to be
> > applied, in a format that I can actually apply them in, I will be glad
> > to do so. But for now, I'd like to get people's systems building again.
> >
>
>
> That would be basically re-adding the b30a43ac7132 commit and adding the
> following patch (also attached in case the inlined version gets mangled):
Thanks for this, I've queued it up now, let's try this all again :)
greg k-h
next prev parent reply other threads:[~2019-06-15 15:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 13:56 Linux 5.1.9 build failure with CONFIG_NOUVEAU_LEGACY_CTX_SUPPORT=n Sven Joachim
2019-06-11 15:36 ` Greg Kroah-Hartman
2019-06-11 17:33 ` Daniel Vetter
2019-06-11 17:40 ` Greg Kroah-Hartman
2019-06-11 19:08 ` Thomas Backlund
2019-06-11 19:42 ` Daniel Vetter
2019-06-11 19:43 ` Sven Joachim
2019-06-11 19:58 ` Thomas Backlund
2019-06-11 19:39 ` Daniel Vetter
2019-06-13 7:42 ` Greg Kroah-Hartman
2019-06-15 10:21 ` Thomas Backlund
2019-06-15 15:27 ` Greg Kroah-Hartman [this message]
2019-06-11 18:53 ` Sven Joachim
2019-06-11 19:41 ` Daniel Vetter
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=20190615152759.GA5171@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=airlied@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=svenjoac@gmx.de \
--cc=tmb@mageia.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).