On Mon, Aug 21, 2023 at 11:30:29AM -0500, Limonciello, Mario wrote: > > > On 8/21/2023 10:37 AM, Greg KH wrote: > > On Mon, Aug 21, 2023 at 02:56:41PM +0200, Greg KH wrote: > > > On Mon, Aug 21, 2023 at 07:15:53AM -0500, Limonciello, Mario wrote: > > > > > > > > > > > > On 8/17/2023 8:40 AM, Alex Deucher wrote: > > > > > From: Tim Huang <Tim.Huang@xxxxxxx> > > > > > > > > > > For SMU v13.0.4/11, driver does not need to stop RLC for S0i3, > > > > > the firmwares will handle that properly. > > > > > > > > > > Signed-off-by: Tim Huang <Tim.Huang@xxxxxxx> > > > > > Reviewed-by: Mario Limonciello <mario.limonciello@xxxxxxx> > > > > > Signed-off-by: Alex Deucher <alexander.deucher@xxxxxxx> > > > > > (cherry picked from commit 730d44e1fa306a20746ad4a85da550662aed9daa) > > > > > Cc: stable@xxxxxxxxxxxxxxx # 6.1.x > > > > > > > > Greg, > > > > > > > > Just want to make sure this one didn't get accidentally skipped since you > > > > populated the stable queues and didn't see it landed. > > > > > > I'm still working on catching up on the stable backlog as I was gone > > > last week, this is in my "to get to soon" queue, it's not lost :) > > > > Wait, I'm confused. You have 2 patches in this series, yet one says > > "6.1.x" and one "6.4.x"? But both actually to both trees. So where are > > these supposed to be applied to? > > > > Please always give me a hint, and never mix/match kernel versions in a > > patch series, what would you do if you recieved that? > > > > thanks, > > > > greg k-h > > Yeah I see the confusion here. Sorry about that. > I looked over both and they should both apply to 6.1.y and 6.4.y. Thanks, both now queued up to both trees. greg k-h