All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas De Marchi <lucas.demarchi@intel.com>
To: Casey Bowman <casey.g.bowman@intel.com>
Cc: intel-gfx@lists.freedesktop.org, daniel.vetter@intel.com
Subject: Re: [Intel-gfx] [PATCH v6 1/1] Split i915_run_as_guest into x86 and non-x86
Date: Tue, 5 Apr 2022 13:06:58 -0700	[thread overview]
Message-ID: <20220405200658.xukfm7y347k6joge@ldmartin-desk2> (raw)
In-Reply-To: <fcf7384d-7ee4-a261-9dd8-8ff0698c3365@intel.com>

On Tue, Apr 05, 2022 at 11:04:54AM -0700, Casey Bowman wrote:
>@Jani/Lucas, any other thoughts here?

last version didn't pass CI:

https://patchwork.freedesktop.org/series/102041/

when this happens, developer should analyze the results to check if it's
a regression from their changes. When it's not a regression we can merge
it, but in this case it didn't pass BAT, so there wasn't even a full
run.

Lucas De Marchi

  reply	other threads:[~2022-04-05 20:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31 20:43 [Intel-gfx] [PATCH v6 0/1] Splitting up platform-specific calls Casey Bowman
2022-03-31 20:43 ` [Intel-gfx] [PATCH v6 1/1] Split i915_run_as_guest into x86 and non-x86 Casey Bowman
2022-04-05 18:04   ` Casey Bowman
2022-04-05 20:06     ` Lucas De Marchi [this message]
2022-04-06 16:24   ` Lucas De Marchi
2022-03-31 22:30 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Splitting up platform-specific calls Patchwork
2022-03-31 23:10 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-04-06  0:41 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Splitting up platform-specific calls (rev2) Patchwork
2022-04-06  0:45 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2022-04-06  1:10 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-04-06  6:21 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=20220405200658.xukfm7y347k6joge@ldmartin-desk2 \
    --to=lucas.demarchi@intel.com \
    --cc=casey.g.bowman@intel.com \
    --cc=daniel.vetter@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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.