linux-kernel - Re: [PATCH 5.15 138/230] drm/amdgpu: bind to any 0x1002 PCI diplay class device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <YsvvXmH9DpMMIIiK@kroah.com>
Date:   Mon, 11 Jul 2022 11:37:34 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Christian König <christian.koenig@....com>
Cc:     Alex Deucher <alexander.deucher@....com>,
        linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        Sasha Levin <sashal@...nel.org>
Subject: Re: [PATCH 5.15 138/230] drm/amdgpu: bind to any 0x1002 PCI diplay
 class device

On Mon, Jul 11, 2022 at 11:29:53AM +0200, Christian König wrote:
> Hi Greg & Alex
> 
> why is that patch picked up for stable? Or are we backporting IP based
> discovery?

New device ids are usually added to stable trees as they are "trivial".

> If yes, is that wise? IIRC we had quite a number of typos etc.. in the
> initial patches.

If this commit is incorrect, we will be glad to drop it, or add any
needed add-on commits.  Which do you want to see happen here?

thanks,

greg k-h