From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Alan Previn <alan.previn.teres.alexis@intel.com>,
intel-gfx@lists.freedesktop.org,
Alexander Usyskin <alexander.usyskin@intel.com>,
dri-devel@lists.freedesktop.org, Vivi@freedesktop.org,
Tomas Winkler <tomas.winkler@intel.com>
Subject: Re: [Intel-gfx] [PATCH v7 3/6] mei: clean pending read with vtag on bus
Date: Fri, 27 Jan 2023 15:26:02 -0500 [thread overview]
Message-ID: <Y9QzWg97bvxvJ71+@intel.com> (raw)
In-Reply-To: <Y9OUy2Ygq2EBzdDV@kroah.com>
On Fri, Jan 27, 2023 at 10:09:31AM +0100, Greg Kroah-Hartman wrote:
> On Wed, Jan 25, 2023 at 12:28:29PM -0500, Rodrigo Vivi wrote:
> >
> > Greg, ack on getting these 3 mei patches merged through intel-gfx?
>
> I only see 2 mei patches in this series, what am I missing?
right... 2 mei patches only... sorry for the noise and for the top posting.
thanks for the ack.
series pushed to drm-intel-next
>
> thanks,
>
> greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Alan Previn <alan.previn.teres.alexis@intel.com>,
Juston Li <justonli@chromium.org>,
intel-gfx@lists.freedesktop.org,
Alexander Usyskin <alexander.usyskin@intel.com>,
dri-devel@lists.freedesktop.org,
Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
Vivi@freedesktop.org, Tomas Winkler <tomas.winkler@intel.com>
Subject: Re: [PATCH v7 3/6] mei: clean pending read with vtag on bus
Date: Fri, 27 Jan 2023 15:26:02 -0500 [thread overview]
Message-ID: <Y9QzWg97bvxvJ71+@intel.com> (raw)
In-Reply-To: <Y9OUy2Ygq2EBzdDV@kroah.com>
On Fri, Jan 27, 2023 at 10:09:31AM +0100, Greg Kroah-Hartman wrote:
> On Wed, Jan 25, 2023 at 12:28:29PM -0500, Rodrigo Vivi wrote:
> >
> > Greg, ack on getting these 3 mei patches merged through intel-gfx?
>
> I only see 2 mei patches in this series, what am I missing?
right... 2 mei patches only... sorry for the noise and for the top posting.
thanks for the ack.
series pushed to drm-intel-next
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2023-01-27 20:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 8:26 [Intel-gfx] [PATCH v7 0/6] drm/i915/pxp: Add missing cleanup steps for PXP global-teardown Alan Previn
2023-01-25 8:26 ` Alan Previn
2023-01-25 8:26 ` [Intel-gfx] [PATCH v7 1/6] mei: mei-me: resume device in prepare Alan Previn
2023-01-25 8:26 ` Alan Previn
2023-01-27 9:08 ` [Intel-gfx] " Greg Kroah-Hartman
2023-01-27 9:08 ` Greg Kroah-Hartman
2023-01-25 8:26 ` [Intel-gfx] [PATCH v7 2/6] drm/i915/pxp: add device link between i915 and mei_pxp Alan Previn
2023-01-25 8:26 ` Alan Previn
2023-01-25 15:53 ` [Intel-gfx] " Rodrigo Vivi
2023-01-25 8:26 ` [Intel-gfx] [PATCH v7 3/6] mei: clean pending read with vtag on bus Alan Previn
2023-01-25 8:26 ` Alan Previn
2023-01-25 17:28 ` [Intel-gfx] " Rodrigo Vivi
2023-01-25 17:28 ` Rodrigo Vivi
2023-01-25 18:01 ` [Intel-gfx] " Greg Kroah-Hartman
2023-01-25 18:01 ` Greg Kroah-Hartman
2023-01-27 9:09 ` [Intel-gfx] " Greg Kroah-Hartman
2023-01-27 9:09 ` Greg Kroah-Hartman
2023-01-27 19:07 ` [Intel-gfx] " Teres Alexis, Alan Previn
2023-01-27 19:07 ` Teres Alexis, Alan Previn
2023-01-27 20:26 ` Rodrigo Vivi [this message]
2023-01-27 20:26 ` Rodrigo Vivi
2023-01-27 9:08 ` [Intel-gfx] " Greg Kroah-Hartman
2023-01-27 9:08 ` Greg Kroah-Hartman
2023-01-25 8:26 ` [Intel-gfx] [PATCH v7 4/6] drm/i915/pxp: Invalidate all PXP fw sessions during teardown Alan Previn
2023-01-25 8:26 ` Alan Previn
2023-01-25 8:26 ` [Intel-gfx] [PATCH v7 5/6] drm/i915/pxp: Trigger the global teardown for before suspending Alan Previn
2023-01-25 8:26 ` Alan Previn
2023-01-25 8:26 ` [Intel-gfx] [PATCH v7 6/6] drm/i915/pxp: Pxp hw init should be in resume_complete Alan Previn
2023-01-25 8:26 ` Alan Previn
2023-01-25 9:40 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/pxp: Add missing cleanup steps for PXP global-teardown Patchwork
2023-01-25 15:11 ` [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=Y9QzWg97bvxvJ71+@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=Vivi@freedesktop.org \
--cc=alan.previn.teres.alexis@intel.com \
--cc=alexander.usyskin@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tomas.winkler@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.