From: "Christian König" <christian.koenig@amd.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>,
Dave Airlie <airlied@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
dri-devel <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] drm fixes for 5.14-rc2
Date: Mon, 19 Jul 2021 08:11:26 +0200 [thread overview]
Message-ID: <44538364-13c5-2626-502c-31d85161a0d4@amd.com> (raw)
In-Reply-To: <20210717214302.mpfil765uji5dnb7@box.shutemov.name>
Am 17.07.21 um 23:43 schrieb Kirill A. Shutemov:
> On Fri, Jul 16, 2021 at 01:41:18PM +1000, Dave Airlie wrote:
>> Hi Linus,
>>
>> Regular rc2 fixes though a bit more than usual at rc2 stage, people
>> must have been testing early or else some fixes from last week got a
>> bit laggy. There is one larger change in the amd fixes to amalgamate
>> some power management code on the newer chips with the code from the
>> older chips, it should only affects chips where support was introduced
>> in rc1 and it should make future fixes easier to maintain probably a
>> good idea to merge it now. Otherwise it's mostly fixes across the
>> board.
>>
>> Dave.
>>
>> drm-fixes-2021-07-16:
>> drm fixes for 5.14-rc2
> Dave, Daniel,
My fault, I've pushed it to drm-misc-next after the branch of.
Just cherry-picked that to drm-misc-fixes. Should be in the next -rc
Thanks for the notice,
Christian.
>
> Looks like the fix[1] for nouveau regression[2] is missing. Hm?
>
> [1] https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore.kernel.org%2Fnouveau%2F20210609172902.1937-1-christian.koenig%40amd.com%2F&data=04%7C01%7Cchristian.koenig%40amd.com%7Cdfa76642807a4953a9dc08d9496bda6a%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637621549856073674%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=8wYkOJYcSoLt3P6cFdTsaYrvX2UEhm7M5RKkaSn5dws%3D&reserved=0
> [2] https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore.kernel.org%2Flkml%2FYOC4uekpD7iA3xPi%40Red%2FT%2F%23u&data=04%7C01%7Cchristian.koenig%40amd.com%7Cdfa76642807a4953a9dc08d9496bda6a%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637621549856073674%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=h5QYbNjhPDAqioojBPTY7uVvfJx6XwEV7ic8rwuMxMc%3D&reserved=0
>
prev parent reply other threads:[~2021-07-19 6:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 3:41 Dave Airlie
2021-07-16 19:28 ` pr-tracker-bot
2021-07-17 21:43 ` Kirill A. Shutemov
2021-07-19 6:11 ` Christian König [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=44538364-13c5-2626-502c-31d85161a0d4@amd.com \
--to=christian.koenig@amd.com \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®