Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>
To: "Usyskin, Alexander" <alexander.usyskin@intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
	David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
	Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: "Winkler, Tomas" <tomas.winkler@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Lubart, Vitaly" <vitaly.lubart@intel.com>
Subject: Re: [Intel-gfx] [PATCH v11 0/5] Add driver for GSC controller
Date: Mon, 28 Mar 2022 10:04:02 -0700	[thread overview]
Message-ID: <26ad86ce-a382-1a65-da78-1c2a03c01a6b@intel.com> (raw)
In-Reply-To: <MW3PR11MB4651A829B5849D219B355D15ED1D9@MW3PR11MB4651.namprd11.prod.outlook.com>

Hi,

Yes, the series doesn't need an update, but on the other hand I don't 
think we can update the config repo before the new config option is 
merged, which we can't do without first running CI with the config 
enabled, so we have a catch-22 situation. That's why I suggested that 
you resend the series with an additional debug patch that enables the 
new config option from within the i915 kconfig, so that CI runs properly 
on it, but clearly marking that patch as something that is for CI only 
and that we shouldn't merge.

We did the same for the mei-pxp config (here's an example: 
https://patchwork.freedesktop.org/patch/460925/?series=96181&rev=2).

The alternative would be to merge an update to i915-infra kconfig/debug 
before this series is merged and re-run CI on the existing series with 
the updated config, but as mentioned above not sure if that's allowed. 
If you can get it in then that's fine for me.

Daniele

On 3/28/2022 12:39 AM, Usyskin, Alexander wrote:
> Hi
>
> As I understand the config patch should go to https://gitlab.freedesktop.org/gfx-ci/i915-infra kconfig/debug, branch "master".
> Thus, this series does not need this change. Am I right?
>


      reply	other threads:[~2022-03-28 17:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-15 13:11 [Intel-gfx] [PATCH v11 0/5] Add driver for GSC controller Alexander Usyskin
2022-03-15 13:11 ` [Intel-gfx] [PATCH v11 1/5] drm/i915/gsc: add gsc as a mei auxiliary device Alexander Usyskin
2022-03-17  1:11   ` Ceraolo Spurio, Daniele
2022-03-15 13:11 ` [Intel-gfx] [PATCH v11 2/5] mei: add support for graphics system controller (gsc) devices Alexander Usyskin
2022-03-17  1:15   ` Ceraolo Spurio, Daniele
2022-03-15 13:11 ` [Intel-gfx] [PATCH v11 3/5] mei: gsc: setup char driver alive in spite of firmware handshake failure Alexander Usyskin
2022-03-15 13:11 ` [Intel-gfx] [PATCH v11 4/5] mei: gsc: add runtime pm handlers Alexander Usyskin
2022-03-22 16:56   ` Rodrigo Vivi
2022-03-15 13:11 ` [Intel-gfx] [PATCH v11 5/5] mei: gsc: retrieve the firmware version Alexander Usyskin
2022-03-15 13:40 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Add driver for GSC controller (rev11) Patchwork
2022-03-15 13:41 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-03-15 14:15 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-15 15:33 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-03-22 20:10 ` [Intel-gfx] [PATCH v11 0/5] Add driver for GSC controller Ceraolo Spurio, Daniele
2022-03-28  7:39   ` Usyskin, Alexander
2022-03-28 17:04     ` Ceraolo Spurio, Daniele [this message]

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=26ad86ce-a382-1a65-da78-1c2a03c01a6b@intel.com \
    --to=daniele.ceraolospurio@intel.com \
    --cc=airlied@linux.ie \
    --cc=alexander.usyskin@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=gregkh@linuxfoundation.org \
    --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=tvrtko.ursulin@linux.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