From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Saarinen, Jani" <jani.saarinen@intel.com>,
"Musial, Ewelina" <ewelina.musial@intel.com>,
"Illipilli, TejasreeX" <tejasreex.illipilli@intel.com>,
LGCI Bug Filing <lgci.bug.filing@intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/dsi: 4th attempt to get rid of IOSF GPIO (rev2)
Date: Wed, 22 Nov 2023 19:17:48 +0200 [thread overview]
Message-ID: <874jhdn1vn.fsf@intel.com> (raw)
In-Reply-To: <DM8PR11MB5655EE430B1F635C70201328E0BAA@DM8PR11MB5655.namprd11.prod.outlook.com>
On Wed, 22 Nov 2023, "Saarinen, Jani" <jani.saarinen@intel.com> wrote:
> Hi,
>> -----Original Message-----
>> From: Musial, Ewelina <ewelina.musial@intel.com>
>> Sent: Wednesday, November 22, 2023 4:25 PM
>> To: Saarinen, Jani <jani.saarinen@intel.com>; Jani Nikula
>> <jani.nikula@linux.intel.com>; Illipilli, TejasreeX <tejasreex.illipilli@intel.com>;
>> LGCI Bug Filing <lgci.bug.filing@intel.com>; Andy Shevchenko
>> <andriy.shevchenko@linux.intel.com>
>> Cc: intel-gfx@lists.freedesktop.org
>> Subject: RE: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/dsi: 4th attempt to get rid
>> of IOSF GPIO (rev2)
>>
>> But this list had only series which were in queue here https://intel-gfx-
>> ci.01.org/queue/index.html and today I was checking exactly how queue for
>> shards is created and there are jobs which are not displayed there. Directly in
>> Jenkins we do have multiple more jobs than in this queue only and I also killed
>> them. I was discussing exactly this case today with Michał and he pointed out that
>> in explanation below queues we do have highlighted:
>> Due to technical limitation this is just an approximation of the queue. It is good
>> for assessing the length of the queue, but should not be considered as
>> completely accurate.
> OK. So could have been in the list but not sure.
Okay, timeout.
I just pushed the series. I trust Hans' testing here, considering the
likely platform impact of the series and CI coverage of said platforms.
Thanks for the patches and review.
BR,
Jani.
>>
>> Regards,
>> Ewelina
>>
>> -----Original Message-----
>> From: Saarinen, Jani <jani.saarinen@intel.com>
>> Sent: Wednesday, November 22, 2023 3:04 PM
>> To: Musial, Ewelina <ewelina.musial@intel.com>; Jani Nikula
>> <jani.nikula@linux.intel.com>; Illipilli, TejasreeX <tejasreex.illipilli@intel.com>;
>> LGCI Bug Filing <lgci.bug.filing@intel.com>; Andy Shevchenko
>> <andriy.shevchenko@linux.intel.com>
>> Cc: intel-gfx@lists.freedesktop.org
>> Subject: RE: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/dsi: 4th attempt to get rid
>> of IOSF GPIO (rev2)
>>
>> HI,
>> > -----Original Message-----
>> > From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of
>> > Musial, Ewelina
>> > Sent: Wednesday, November 22, 2023 3:39 PM
>> > To: Jani Nikula <jani.nikula@linux.intel.com>; Illipilli, TejasreeX
>> > <tejasreex.illipilli@intel.com>; LGCI Bug Filing
>> > <lgci.bug.filing@intel.com>; Andy Shevchenko
>> > <andriy.shevchenko@linux.intel.com>
>> > Cc: intel-gfx@lists.freedesktop.org
>> > Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/dsi: 4th
>> > attempt to get rid of IOSF GPIO (rev2)
>> >
>> > Hi, I reviewed what I could, and my conclusion is that CI.FULL for
>> > this series was killed due to my work around 126526v6 - yesterday I
>> > was asked to do whatever I can to speed up shards testing for
>> > mentioned series and I killed multiple sessions which were higher in
>> > queue. We do not have option to simply bump priority for premerge
>> > series and the only way (not recommended but sometimes needed) is to
>> > drop everything what is higher. I've added this series back to queue.
>> > Sorry for inconvenience
>> Nope. It was not part of that list. We checked that with Jani too. See those
>> pictures we discussed.
>> >
>> > Regards,
>> > Ewelina
>>
>> Br,
>> Jani S
--
Jani Nikula, Intel
next prev parent reply other threads:[~2023-11-22 17:18 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 20:18 [Intel-gfx] [rft, PATCH v4 00/16] drm/i915/dsi: 4th attempt to get rid of IOSF GPIO Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` [Intel-gfx] [PATCH v4 01/16] drm/i915/dsi: assume BXT gpio works for non-native GPIO Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` [Intel-gfx] [PATCH v4 02/16] drm/i915/dsi: switch mipi_exec_gpio() from dev_priv to i915 Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` [Intel-gfx] [PATCH v4 03/16] drm/i915/dsi: clarify GPIO exec sequence Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` [Intel-gfx] [PATCH v4 04/16] drm/i915/dsi: rename platform specific *_exec_gpio() to *_gpio_set_value() Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` [Intel-gfx] [PATCH v4 05/16] drm/i915/dsi: bxt/icl GPIO set value do not need gpio source Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` [Intel-gfx] [PATCH v4 06/16] drm/i915/dsi: Replace while(1) with one with clear exit condition Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` [Intel-gfx] [PATCH v4 07/16] drm/i915/dsi: Get rid of redundant 'else' Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` [Intel-gfx] [PATCH v4 08/16] drm/i915/dsi: Replace check with a (missing) MIPI sequence name Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` [Intel-gfx] [PATCH v4 09/16] drm/i915/dsi: Remove GPIO lookup table at the end of intel_dsi_vbt_gpio_init() Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` [Intel-gfx] [PATCH v4 10/16] drm/i915/dsi: Fix wrong initial value for GPIOs in bxt_gpio_set_value() Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` [Intel-gfx] [PATCH v4 11/16] drm/i915/dsi: Extract common soc_gpio_set_value() helper Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` [Intel-gfx] [PATCH v4 12/16] drm/i915/dsi: Replace poking of VLV GPIOs behind the driver's back Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` [Intel-gfx] [PATCH v4 13/16] drm/i915/dsi: Prepare soc_gpio_set_value() to distinguish GPIO communities Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` [Intel-gfx] [PATCH v4 14/16] drm/i915/dsi: Replace poking of CHV GPIOs behind the driver's back Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` [Intel-gfx] [PATCH v4 15/16] drm/i915/dsi: Combine checks in mipi_exec_gpio() Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` [Intel-gfx] [PATCH v4 16/16] drm/i915/iosf: Drop unused APIs Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 20:18 ` Andy Shevchenko
2023-11-03 22:22 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dsi: 4th attempt to get rid of IOSF GPIO Patchwork
2023-11-03 22:41 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-11-16 8:58 ` [Intel-gfx] [rft, PATCH v4 00/16] " Hans de Goede
2023-11-16 8:58 ` Hans de Goede
2023-11-16 8:58 ` Hans de Goede
2023-11-16 10:15 ` [Intel-gfx] " Jani Nikula
2023-11-16 10:15 ` Jani Nikula
2023-11-16 10:15 ` Jani Nikula
2023-11-17 21:05 ` [Intel-gfx] " Andy Shevchenko
2023-11-17 21:05 ` Andy Shevchenko
2023-11-17 21:05 ` Andy Shevchenko
2023-11-21 10:28 ` [Intel-gfx] " Jani Nikula
2023-11-21 10:28 ` Jani Nikula
2023-11-21 10:28 ` Jani Nikula
2023-11-17 21:06 ` [Intel-gfx] " Andy Shevchenko
2023-11-17 21:06 ` Andy Shevchenko
2023-11-17 21:06 ` Andy Shevchenko
2023-11-16 12:39 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dsi: 4th attempt to get rid of IOSF GPIO (rev2) Patchwork
2023-11-16 12:57 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-11-16 16:59 ` Jani Nikula
2023-11-21 10:43 ` Illipilli, TejasreeX
2023-11-22 10:55 ` Jani Nikula
2023-11-22 11:14 ` Andy Shevchenko
2023-11-22 13:38 ` Musial, Ewelina
2023-11-22 14:04 ` Saarinen, Jani
2023-11-22 14:24 ` Musial, Ewelina
2023-11-22 15:01 ` Saarinen, Jani
2023-11-22 17:17 ` Jani Nikula [this message]
2023-11-22 17:30 ` Andy Shevchenko
2023-11-23 6:46 ` Musial, Ewelina
2023-11-16 18:41 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dsi: 4th attempt to get rid of IOSF GPIO (rev4) Patchwork
2023-11-16 18:59 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-11-20 23:55 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dsi: 4th attempt to get rid of IOSF GPIO (rev5) Patchwork
2023-11-21 0:14 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-11-21 9:27 ` Jani Nikula
2023-11-21 10:22 ` [Intel-gfx] ✓ Fi.CI.BAT: success " 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=874jhdn1vn.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ewelina.musial@intel.com \
--cc=hdegoede@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.saarinen@intel.com \
--cc=lgci.bug.filing@intel.com \
--cc=tejasreex.illipilli@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.