Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Tomas Winkler <tomas.winkler@intel.com>,
	Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Cc: Alan Previn <alan.previn.teres.alexis@intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	intel-gfx@lists.freedesktop.org,
	Alexander Usyskin <alexander.usyskin@intel.com>,
	linux-kernel@vger.kernel.org,
	Vitaly Lubart <vitaly.lubart@intel.com>
Subject: Re: [Intel-gfx] [char-misc-next v3 0/2] mei: gsc proxy component
Date: Wed, 8 Feb 2023 12:17:23 -0500	[thread overview]
Message-ID: <Y+PZI/mfxwSNmy8R@intel.com> (raw)
In-Reply-To: <20230208142358.1401618-1-tomas.winkler@intel.com>

On Wed, Feb 08, 2023 at 04:23:56PM +0200, Tomas Winkler wrote:
> GSC Proxy component is used for communication between the
> Intel graphics driver and MEI driver.
> 
> Daniele, please ack so that drm part can be merged via Greg's tree.

Cc: Daniele, since he was missing on this submission.

He raise concerns on getting this through another tree since he
has a pending series that uses this interface here. The propagation
at this point will take so long.

Could we do the other way around and get Greg's and your, Thomas',
acks to merge this through our drm-intel trees?

> 
> V2:
> 1. Add missing patch from the series
> 2. Use device information instead of driver name
>    to identify the aggregate device.
> V3:
> 1. Drop MAINTAINERS update
> 2. Add gfx mailing list and maintanier
> 
> 
> Alexander Usyskin (2):
>   drm/i915/mtl: Define GSC Proxy component interface
>   mei: gsc_proxy: add gsc proxy driver
> 
>  drivers/misc/mei/Kconfig                   |   2 +-
>  drivers/misc/mei/Makefile                  |   1 +
>  drivers/misc/mei/gsc_proxy/Kconfig         |  14 ++
>  drivers/misc/mei/gsc_proxy/Makefile        |   7 +
>  drivers/misc/mei/gsc_proxy/mei_gsc_proxy.c | 208 +++++++++++++++++++++
>  include/drm/i915_component.h               |   3 +-
>  include/drm/i915_gsc_proxy_mei_interface.h |  36 ++++
>  7 files changed, 269 insertions(+), 2 deletions(-)
>  create mode 100644 drivers/misc/mei/gsc_proxy/Kconfig
>  create mode 100644 drivers/misc/mei/gsc_proxy/Makefile
>  create mode 100644 drivers/misc/mei/gsc_proxy/mei_gsc_proxy.c
>  create mode 100644 include/drm/i915_gsc_proxy_mei_interface.h
> 
> -- 
> 2.39.1
> 

  parent reply	other threads:[~2023-02-08 17:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 14:23 [Intel-gfx] [char-misc-next v3 0/2] mei: gsc proxy component Tomas Winkler
2023-02-08 14:23 ` [Intel-gfx] [char-misc-next v3 1/2] drm/i915/mtl: Define GSC Proxy component interface Tomas Winkler
2023-02-08 14:23 ` [Intel-gfx] [char-misc-next v3 2/2] mei: gsc_proxy: add gsc proxy driver Tomas Winkler
2023-02-08 14:55 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for mei: gsc proxy component Patchwork
2023-02-08 17:17 ` Rodrigo Vivi [this message]
2023-02-08 17:32   ` [Intel-gfx] [char-misc-next v3 0/2] " Greg Kroah-Hartman
2023-02-08 18:59 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-02-09  8:02 ` [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=Y+PZI/mfxwSNmy8R@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=alan.previn.teres.alexis@intel.com \
    --cc=alexander.usyskin@intel.com \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --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