From: Andi Shyti <andi.shyti@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Michael Cheng" <michael.cheng@intel.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"David Airlie" <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
"Chris Wilson" <chris.p.wilson@intel.com>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Matthew Auld" <matthew.auld@intel.com>
Subject: Re: [Intel-gfx] [PATCH v3 1/3] drm/i915: pass a pointer for tlb seqno at vma_invalidate_tlb()
Date: Tue, 9 Aug 2022 01:09:51 +0200 [thread overview]
Message-ID: <YvGXv5td47ky+CnY@alfio.lan> (raw)
In-Reply-To: <YvFeLbUcC6yiCL5G@intel.com>
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@kernel.org>
> >
> > Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
>
> 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.
Andi
> Thanks,
> Rodrigo.
>
> >
> > Andi
WARNING: multiple messages have this Message-ID (diff)
From: Andi Shyti <andi.shyti@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Michael Cheng" <michael.cheng@intel.com>,
"David Airlie" <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
"Chris Wilson" <chris.p.wilson@intel.com>,
"Andi Shyti" <andi.shyti@linux.intel.com>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Matthew Auld" <matthew.auld@intel.com>
Subject: Re: [Intel-gfx] [PATCH v3 1/3] drm/i915: pass a pointer for tlb seqno at vma_invalidate_tlb()
Date: Tue, 9 Aug 2022 01:09:51 +0200 [thread overview]
Message-ID: <YvGXv5td47ky+CnY@alfio.lan> (raw)
In-Reply-To: <YvFeLbUcC6yiCL5G@intel.com>
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@kernel.org>
> >
> > Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
>
> 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.
Andi
> Thanks,
> Rodrigo.
>
> >
> > Andi
next prev parent reply other threads:[~2022-08-08 23:10 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 7:37 [Intel-gfx] [PATCH v3 0/3] Move TLB invalidation code for its own file and document it Mauro Carvalho Chehab
2022-08-04 7:37 ` Mauro Carvalho Chehab
2022-08-04 7:37 ` Mauro Carvalho Chehab
2022-08-04 7:37 ` [Intel-gfx] [PATCH v3 1/3] drm/i915: pass a pointer for tlb seqno at vma_invalidate_tlb() Mauro Carvalho Chehab
2022-08-04 7:37 ` Mauro Carvalho Chehab
2022-08-04 8:18 ` [Intel-gfx] " Tvrtko Ursulin
2022-08-04 8:18 ` Tvrtko Ursulin
2022-08-08 16:37 ` [Intel-gfx] " Andi Shyti
2022-08-08 16:37 ` Andi Shyti
2022-08-08 19:04 ` [Intel-gfx] " Rodrigo Vivi
2022-08-08 19:04 ` Rodrigo Vivi
2022-08-08 23:09 ` Andi Shyti [this message]
2022-08-08 23:09 ` Andi Shyti
2022-08-09 0:15 ` Vivi, Rodrigo
2022-08-09 0:15 ` Vivi, Rodrigo
2022-08-09 6:29 ` Mauro Carvalho Chehab
2022-08-09 6:29 ` Mauro Carvalho Chehab
2022-08-04 7:37 ` [Intel-gfx] [PATCH v3 2/3] drm/i915/gt: Move TLB invalidation to its own file Mauro Carvalho Chehab
2022-08-04 7:37 ` Mauro Carvalho Chehab
2022-08-04 7:37 ` [Intel-gfx] [PATCH v3 3/3] drm/i915/gt: document TLB cache invalidation functions Mauro Carvalho Chehab
2022-08-04 7:37 ` Mauro Carvalho Chehab
2022-08-04 7:37 ` Mauro Carvalho Chehab
2022-08-04 19:00 ` [Intel-gfx] " Randy Dunlap
2022-08-04 19:00 ` Randy Dunlap
2022-08-04 19:00 ` Randy Dunlap
2022-08-05 9:08 ` [Intel-gfx] " Andi Shyti
2022-08-05 9:08 ` Andi Shyti
2022-08-05 9:08 ` Andi Shyti
2022-08-05 9:24 ` [Intel-gfx] " Tvrtko Ursulin
2022-08-05 9:24 ` Tvrtko Ursulin
2022-08-05 9:24 ` Tvrtko Ursulin
2022-08-05 10:30 ` [Intel-gfx] " Mauro Carvalho Chehab
2022-08-05 10:30 ` Mauro Carvalho Chehab
2022-08-05 10:30 ` Mauro Carvalho Chehab
2022-08-08 16:58 ` Andi Shyti
2022-08-08 16:58 ` Andi Shyti
2022-08-08 16:58 ` Andi Shyti
2022-08-04 8:12 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Move TLB invalidation code for its own file and document it (rev4) Patchwork
2022-08-04 8:12 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-08-04 8:34 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-08-04 10:09 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=YvGXv5td47ky+CnY@alfio.lan \
--to=andi.shyti@linux.intel.com \
--cc=airlied@linux.ie \
--cc=chris.p.wilson@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.auld@intel.com \
--cc=mchehab@kernel.org \
--cc=michael.cheng@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=thomas.hellstrom@linux.intel.com \
/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.