From: Willy Tarreau <w@1wt.eu>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Ilia Mirkin <imirkin@alum.mit.edu>,
stable <stable@vger.kernel.org>,
"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, 1 Mar 2016 07:19:32 +0100 [thread overview]
Message-ID: <20160301061932.GA17676@1wt.eu> (raw)
In-Reply-To: <20160301055843.GC3200@kroah.com>
On Tue, Mar 01, 2016 at 05:58:44AM +0000, Greg KH wrote:
> On Sun, Jan 17, 2016 at 02:28:13PM -0500, Ilia Mirkin wrote:
> > Hello,
> >
> > 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
>
> It doesn't apply to 3.14-stable at all :(
I just checked, the path to the file changed, in 3.14 you need to
replace "/nvkm/" with "/core/". However given that all entries in
the switch/case are nearly identical, there are great chances for
this patch to be applied at the wrong positioni (it targets 0x46),
I guess someone who owns this hardware should provide the backport
after testing it to ensure it applies at the right position and
really works.
Willy
prev parent reply other threads:[~2016-03-01 6:19 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
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 [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=20160301061932.GA17676@1wt.eu \
--to=w@1wt.eu \
--cc=bskeggs@redhat.com \
--cc=gregkh@linuxfoundation.org \
--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).