From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
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: Wed, 25 Jan 2023 19:01:29 +0100 [thread overview]
Message-ID: <Y9FueZmoVZchi6zW@kroah.com> (raw)
In-Reply-To: <Y9FmvUujJeijwZXi@intel.com>
Why are you top posting?
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?
$ mdfrm -c ~/mail/todo/
756 messages in /home/gregkh/mail/todo/
Give me a chance, what is the sudden rush?
greg k-h
next prev parent reply other threads:[~2023-01-25 18:01 UTC|newest]
Thread overview: 17+ 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 ` [Intel-gfx] [PATCH v7 1/6] mei: mei-me: resume device in prepare Alan Previn
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 15:53 ` 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 17:28 ` Rodrigo Vivi
2023-01-25 18:01 ` Greg Kroah-Hartman [this message]
2023-01-27 9:09 ` Greg Kroah-Hartman
2023-01-27 19:07 ` Teres Alexis, Alan Previn
2023-01-27 20:26 ` Rodrigo Vivi
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 ` [Intel-gfx] [PATCH v7 5/6] drm/i915/pxp: Trigger the global teardown for before suspending 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 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=Y9FueZmoVZchi6zW@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Vivi@freedesktop.org \
--cc=alan.previn.teres.alexis@intel.com \
--cc=alexander.usyskin@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox