On Tue, 9 Aug 2022 00:15:14 +0000 "Vivi, Rodrigo" <rodrigo.vivi@xxxxxxxxx> wrote: > On Tue, 2022-08-09 at 01:09 +0200, Andi Shyti wrote: > > Hi Rodrigo, > > > > On Mon, Aug 08, 2022 at 03:04:13PM -0400, Rodrigo Vivi wrote: > > > On Mon, Aug 08, 2022 at 06:37:58PM +0200, Andi Shyti wrote: > > > > Hi Mauro, > > > > > > > > On Thu, Aug 04, 2022 at 09:37:22AM +0200, Mauro Carvalho Chehab > > > > wrote: > > > > > WRITE_ONCE() should happen at the original var, not on a local > > > > > copy of it. > > > > > > > > > > Fixes: 5d36acb7198b ("drm/i915/gt: Batch TLB invalidations") > > > > > Signed-off-by: Mauro Carvalho Chehab <mchehab@xxxxxxxxxx> > > > > > > > > Reviewed-by: Andi Shyti <andi.shyti@xxxxxxxxxxxxxxx> > > > > > > Thanks and pushed... > > > > Thanks! > > > > > > > > > > Are you going to send it to the stable mailing list? > > > > > > I added cc stable while pushing and the cherry-pick to drm-intel- > > > next-fixes > > > has the right sha, so I'd assume this would be automagically now. > > > But yeap, it would be good if Mauro can follow up whenever this > > > gets > > > to Linus tree and Greg's script start to pop up the heads-up > > > messages. > > > > That's what I meant... does Mauro now need to send the e-mail > > again for the stable? > > > > I thought there was some suspicion towards e-mails pushed without > > being first sent to both stable and upstream mailing lists > > because they can get lost or forgotten... maybe I'm wrong. > > It doesn't help to send now to stable ml because it can only be merged > there after it reaches the Linus' master tree. > Right now with the right fixes and cc:stable it should be automatically > and he shouldn't worry. > But in case he notices that the first patch got in but the second > didn't then it is when we send the patch directly to the stable ml. I sent a heads-up to Greg to warn him about the issue. I'll keep my eyes on the -stable automatic e-mails to double-check that they'll both be merged altogether. Thanks! Mauro > > > > > > Andi > > > > > Thanks, > > > Rodrigo. > > > > > > > > > > > Andi >