From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alexander Usyskin <alexander.usyskin@intel.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Tomas Winkler <tomas.winkler@intel.com>,
Vitaly Lubart <vitaly.lubart@intel.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/5] Add driver for GSC controller
Date: Thu, 27 Jan 2022 12:31:07 +0100 [thread overview]
Message-ID: <YfKCe9ALCjrUO+89@kroah.com> (raw)
In-Reply-To: <20220127112103.2336871-1-alexander.usyskin@intel.com>
On Thu, Jan 27, 2022 at 01:20:58PM +0200, Alexander Usyskin wrote:
> GSC is a graphics system controller, it provides
> a chassis controller for graphics discrete cards.
>
> There are two MEI interfaces in GSC: HECI1 and HECI2.
>
> This series includes instantiation of the auxiliary devices for HECI2
> and mei-gsc auxiliary device driver that binds to the auxiliary device.
>
> In v2 the platform device was replaced by the auxiliary device.
> v3 is the rebase over drm-tip to make public CI running.
> In v4 the not needed debug prints and empty line were removed,
> 'select' were replaced by 'depends on' in MEI Kconfig,
> the new include file now listed in the MAINTATINERS file.
>
> Greg KH, please review and ACK the MEI patches after main merge window closure.
The merge window already closed, did you forget to update your email?
> We are pushing all through gfx tree as the auxiliary device belongs there.
I'll get to this in a week or so, please be patient.
greg k-h
next prev parent reply other threads:[~2022-01-27 11:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 11:20 [PATCH v4 0/5] Add driver for GSC controller Alexander Usyskin
2022-01-27 11:20 ` [PATCH v4 1/5] drm/i915/gsc: add gsc as a mei auxiliary device Alexander Usyskin
2022-01-27 11:21 ` [PATCH v4 2/5] mei: add support for graphics system controller (gsc) devices Alexander Usyskin
2022-01-27 11:21 ` [PATCH v4 3/5] mei: gsc: setup char driver alive in spite of firmware handshake failure Alexander Usyskin
2022-01-27 11:21 ` [PATCH v4 4/5] mei: gsc: add runtime pm handlers Alexander Usyskin
2022-01-27 11:21 ` [PATCH v4 5/5] mei: gsc: retrieve the firmware version Alexander Usyskin
2022-01-27 11:31 ` Greg Kroah-Hartman [this message]
2022-01-27 11:31 ` [PATCH v4 0/5] Add driver for GSC controller Greg Kroah-Hartman
2022-02-04 15:29 ` Greg Kroah-Hartman
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=YfKCe9ALCjrUO+89@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=airlied@linux.ie \
--cc=alexander.usyskin@intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=tomas.winkler@intel.com \
--cc=vitaly.lubart@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