From: Greg KH <greg@kroah.com>
To: Maxim Sheviakov <mrader3940@gmail.com>
Cc: Alex Deucher <alexander.deucher@amd.com>, stable@vger.kernel.org
Subject: Re: Cherry-pick Pitcairn quirk drop code from master
Date: Sat, 4 Mar 2017 10:16:30 +0100 [thread overview]
Message-ID: <20170304091630.GC17756@kroah.com> (raw)
In-Reply-To: <20170304083108.27945-1-mrader3940@gmail.com>
On Sat, Mar 04, 2017 at 11:31:08AM +0300, Maxim Sheviakov wrote:
> This is just a kinda cherry-pick from linux-4.11, which already contains this, to v4.10. It shouldn't
> break stuff, because all the firmware is alreay in linux-firmware.git. It is, however, reported that
> using AMDGPU on Pitcairn chips with this patch applied may prevent Xorg from working properly, but it looks
> like an issue in the experimental SI support code out there, so RADEON users should be just fine.
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read Documentation/stable_kernel_rules.txt
for how to do this properly.
</formletter>
prev parent reply other threads:[~2017-03-04 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 8:31 Cherry-pick Pitcairn quirk drop code from master Maxim Sheviakov
2017-03-04 9:16 ` Greg KH [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=20170304091630.GC17756@kroah.com \
--to=greg@kroah.com \
--cc=alexander.deucher@amd.com \
--cc=mrader3940@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.