All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lucas De Marchi <lucas.demarchi@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx]  ✗ Fi.CI.BUILD: failure for Prefer acronym for prefixes (rev2)
Date: Mon, 23 Dec 2019 12:05:53 -0800	[thread overview]
Message-ID: <20191223200553.n5yruhossmzuwhes@ldmartin-desk1> (raw)
In-Reply-To: <157712965604.16935.7402888261784935239@emeril.freedesktop.org>

On Mon, Dec 23, 2019 at 07:34:16PM +0000, Patchwork wrote:
>== Series Details ==
>
>Series: Prefer acronym for prefixes (rev2)
>URL   : https://patchwork.freedesktop.org/series/71224/
>State : failure
>
>== Summary ==
>
>Applying: drm/i915: simplify prefixes on device_info
>Applying: drm/i915: prefer 3-letter acronym for pineview
>Applying: drm/i915: prefer 3-letter acronym for haswell
>Applying: drm/i915: prefer 3-letter acronym for skylake
>Applying: drm/i915: prefer 3-letter acronym for cannonlake
>Applying: drm/i915: prefer 3-letter acronym for icelake
>Applying: drm/i915: prefer 3-letter acronym for ironlake
>error: sha1 information is lacking or useless (drivers/gpu/drm/i915/display/intel_display.c).
>error: could not build fake ancestor
>hint: Use 'git am --show-current-patch' to see the failed patch
>Patch failed at 0007 drm/i915: prefer 3-letter acronym for ironlake
>When you have resolved this problem, run "git am --continue".
>If you prefer to skip this patch, run "git am --skip" instead.
>To restore the original branch and stop patching, run "git am --abort".

poor bot, dim retip works ok here. I will wait to see if I get r-b
before sending another rebase of these trivial changes.

Lucas De Marchi


>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2019-12-23 20:06 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-23 17:32 [Intel-gfx] [PATCH v3 00/10] Prefer acronym for prefixes Lucas De Marchi
2019-12-23 17:32 ` [Intel-gfx] [PATCH v3 01/10] drm/i915: simplify prefixes on device_info Lucas De Marchi
2019-12-23 22:56   ` Matt Roper
2019-12-23 17:32 ` [Intel-gfx] [PATCH v3 02/10] drm/i915: prefer 3-letter acronym for pineview Lucas De Marchi
2019-12-23 22:58   ` Matt Roper
2019-12-23 23:20     ` Lucas De Marchi
2019-12-23 23:23       ` Matt Roper
2019-12-23 17:32 ` [Intel-gfx] [PATCH v3 03/10] drm/i915: prefer 3-letter acronym for haswell Lucas De Marchi
2019-12-23 23:00   ` Matt Roper
2019-12-23 17:32 ` [Intel-gfx] [PATCH v3 04/10] drm/i915: prefer 3-letter acronym for skylake Lucas De Marchi
2019-12-23 23:01   ` Matt Roper
2019-12-23 17:32 ` [Intel-gfx] [PATCH v3 05/10] drm/i915: prefer 3-letter acronym for cannonlake Lucas De Marchi
2019-12-23 23:04   ` Matt Roper
2019-12-23 17:32 ` [Intel-gfx] [PATCH v3 06/10] drm/i915: prefer 3-letter acronym for icelake Lucas De Marchi
2019-12-23 23:08   ` Matt Roper
2019-12-23 17:32 ` [Intel-gfx] [PATCH v3 07/10] drm/i915: prefer 3-letter acronym for ironlake Lucas De Marchi
2019-12-23 23:13   ` Matt Roper
2019-12-23 23:22     ` Lucas De Marchi
2019-12-23 23:23       ` Matt Roper
2019-12-23 17:32 ` [Intel-gfx] [PATCH v3 08/10] drm/i915: prefer 3-letter acronym for broadwell Lucas De Marchi
2019-12-23 23:15   ` Matt Roper
2019-12-23 17:32 ` [Intel-gfx] [PATCH v3 09/10] drm/i915: prefer 3-letter acronym for ivybridge Lucas De Marchi
2019-12-23 23:16   ` Matt Roper
2019-12-23 17:32 ` [Intel-gfx] [PATCH v3 10/10] drm/i915: prefer 3-letter acronym for tigerlake Lucas De Marchi
2019-12-23 23:17   ` Matt Roper
2019-12-23 19:34 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Prefer acronym for prefixes (rev2) Patchwork
2019-12-23 20:05   ` Lucas De Marchi [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=20191223200553.n5yruhossmzuwhes@ldmartin-desk1 \
    --to=lucas.demarchi@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.