public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Tomas Winkler <tomas.winkler@intel.com>
Cc: Alexander Usyskin <alexander.usyskin@intel.com>,
	Vitaly Lubart <vitaly.lubart@intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [char-misc-next v2 1/2] drm/i915/mtl: Define GSC Proxy component interface
Date: Wed, 8 Feb 2023 13:26:56 +0100	[thread overview]
Message-ID: <Y+OVEGNnQXZSxNdG@kroah.com> (raw)
In-Reply-To: <20230205181132.191064-2-tomas.winkler@intel.com>

On Sun, Feb 05, 2023 at 08:11:31PM +0200, Tomas Winkler wrote:
> From: Alexander Usyskin <alexander.usyskin@intel.com>
> 
> GSC Proxy component is used for communication between the
> Intel graphics driver and MEI driver.
> 
> Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
> Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
> ---
> V2: This patch was missing in the first series.
> 
>  MAINTAINERS                                |  1 +
>  include/drm/i915_component.h               |  3 +-
>  include/drm/i915_gsc_proxy_mei_interface.h | 36 ++++++++++++++++++++++
>  3 files changed, 39 insertions(+), 1 deletion(-)
>  create mode 100644 include/drm/i915_gsc_proxy_mei_interface.h


Why do you add .h files in include/drm/ yet only use them in
drivers/mei/ ?

Shouldn't they just live in the mei subdir?  Especially given that you
also want to maintain them through the mei subsystem as per this change:

> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index c81bbb771678..2c432b4d8506 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -10570,6 +10570,7 @@ S:	Supported
>  F:	Documentation/driver-api/mei/*
>  F:	drivers/misc/mei/
>  F:	drivers/watchdog/mei_wdt.c
> +F:	include/drm/i915_gsc_proxy_mei_interface.h
>  F:	include/linux/mei_aux.h
>  F:	include/linux/mei_cl_bus.h
>  F:	include/uapi/linux/mei.h

And I would need some i915 maintainer acks before I could take this in
my tree.

thanks,

greg k-h

  reply	other threads:[~2023-02-08 12:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-05 18:11 [char-misc-next v2 0/2] mei: gsc proxy component Tomas Winkler
2023-02-05 18:11 ` [char-misc-next v2 1/2] drm/i915/mtl: Define GSC Proxy component interface Tomas Winkler
2023-02-08 12:26   ` Greg Kroah-Hartman [this message]
2023-02-08 12:35     ` Winkler, Tomas
2023-02-05 18:11 ` [char-misc-next v2 2/2] mei: gsc_proxy: add gsc proxy driver Tomas Winkler
2023-02-08 12:27   ` 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=Y+OVEGNnQXZSxNdG@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alexander.usyskin@intel.com \
    --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