From: Jiri Slaby <jslaby@suse.cz>
To: Ilia Mirkin <imirkin@alum.mit.edu>, stable <stable@vger.kernel.org>
Cc: "nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
Hans de Goede <hdegoede@redhat.com>,
Ben Skeggs <bskeggs@redhat.com>
Subject: Re: Recommendation for cherry-pick between 3.12 and 4.2: 0a363e85cdaf
Date: Tue, 19 Jan 2016 11:22:11 +0100 [thread overview]
Message-ID: <569E0E53.4010201@suse.cz> (raw)
In-Reply-To: <CAKb7UvhmjD5HfNRDwR8phUhFwYhGS0QPMMucnNc+YWZUb5M-dg@mail.gmail.com>
Hi,
On 01/17/2016, 08:28 PM, Ilia Mirkin wrote:
> I'd like to recommend backporting this commit:
>
> commit 0a363e85cdafbceeee6a49b91c604d0d4d070dc7
> Author: Hans de Goede <hdegoede@redhat.com>
> Date: Thu Jul 23 17:20:12 2015 +0200
>
> drm/nouveau/nv46: Change mc subdev oclass from nv44 to nv4c
>
> This disables MSI by default on G72 (NV46) devices where it's
> apparently a bit buggy. We have a later patch which turns MSI back on
> with a quirk, but it isn't extremely necessary for these devices, and
> disabling (or, rather, not enabling) MSI is a pretty safe thing to do.
>
> The patch went upstream in 4.3-rc1, however I believe that there are
> still a number of kernels between 3.12 (where MSI was first enabled by
> default - commit a27e56996) and 4.2 (inclusive) which are still being
> maintained. To those maintainers, please consider including this in
> your trees.
But it needs
commit fa8c9ac72fe0bcdf5bc7cc84e85cc2a1af53f9fd
Author: Ilia Mirkin <imirkin@alum.mit.edu>
Date: Wed Feb 5 14:33:02 2014 -0500
drm/nv4c/mc: nv4x igp's have a different msi rearm register
See https://bugs.freedesktop.org/show_bug.cgi?id=74492
which is only in 3.14. So I cannot take it into 3.12.
thanks,
--
js
suse labs
next prev parent reply other threads:[~2016-01-19 10:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 19:28 Recommendation for cherry-pick between 3.12 and 4.2: 0a363e85cdaf Ilia Mirkin
2016-01-19 10:22 ` Jiri Slaby [this message]
2016-01-19 11:03 ` Ilia Mirkin
2016-01-19 13:53 ` Jiri Slaby
2016-01-26 18:14 ` Kamal Mostafa
2016-01-27 14:24 ` Luis Henriques
2016-03-01 5:58 ` Greg KH
2016-03-01 6:19 ` Willy Tarreau
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=569E0E53.4010201@suse.cz \
--to=jslaby@suse.cz \
--cc=bskeggs@redhat.com \
--cc=hdegoede@redhat.com \
--cc=imirkin@alum.mit.edu \
--cc=nouveau@lists.freedesktop.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).