All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Zheng Hacker" <hackerzheng666@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915/gvt: fix double-free bug in split_2MB_gtt_entry.
Date: Tue, 06 Sep 2022 12:58:11 -0000	[thread overview]
Message-ID: <166246909164.8880.10585519190282207260@emeril.freedesktop.org> (raw)
In-Reply-To: <tencent_E1BBF05904DFB73C478DCD592740AAE0780A@qq.com>

== Series Details ==

Series: drm/i915/gvt: fix double-free bug in split_2MB_gtt_entry.
URL   : https://patchwork.freedesktop.org/series/108188/
State : failure

== Summary ==

Error: patch https://patchwork.freedesktop.org/api/1.0/series/108188/revisions/1/mbox/ not applied
Applying: drm/i915/gvt: fix double-free bug in split_2MB_gtt_entry.
error: patch failed: drivers/gpu/drm/i915/gvt/gtt.c:1215
error: drivers/gpu/drm/i915/gvt/gtt.c: patch does not apply
error: Did you hand edit your patch?
It does not apply to blobs recorded in its index.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Using index info to reconstruct a base tree...
Patch failed at 0001 drm/i915/gvt: fix double-free bug in split_2MB_gtt_entry.
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".



  parent reply	other threads:[~2022-09-06 12:58 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tencent_E1BBF05904DFB73C478DCD592740AAE0780A@qq.com>
2022-09-05  4:47 ` [PATCH] drm/i915/gvt: fix double-free bug in split_2MB_gtt_entry Zheng Hacker
2022-09-05  4:47   ` [Intel-gfx] " Zheng Hacker
2022-09-05  6:11   ` Zheng Hacker
2022-09-05  6:11     ` [Intel-gfx] " Zheng Hacker
2022-09-05  7:35   ` Zheng Hacker
2022-09-05  7:35     ` [Intel-gfx] " Zheng Hacker
2022-09-05  7:35     ` Zheng Hacker
2022-09-05  7:46     ` Zheng Hacker
2022-09-05  7:46       ` [Intel-gfx] " Zheng Hacker
2022-09-05  7:46       ` Zheng Hacker
2022-09-05  8:04       ` Greg KH
2022-09-05  8:04         ` [Intel-gfx] " Greg KH
2022-09-05  8:04         ` Greg KH
2022-09-05  8:53         ` Alex Young
2022-09-05  8:53           ` Alex Young
2022-09-06 11:36         ` Zheng Hacker
2022-09-06 11:36           ` [Intel-gfx] " Zheng Hacker
2022-09-06 11:36           ` Zheng Hacker
2022-09-07  3:07           ` Zhenyu Wang
2022-09-07  3:07             ` [Intel-gfx] " Zhenyu Wang
2022-09-07  3:07             ` Zhenyu Wang
2022-09-07  6:47             ` Zheng Hacker
2022-09-07  6:47               ` [Intel-gfx] " Zheng Hacker
2022-09-07  6:47               ` Zheng Hacker
2022-09-08  9:09             ` Zheng Hacker
2022-09-08  9:09               ` [Intel-gfx] " Zheng Hacker
2022-09-08  9:09               ` Zheng Hacker
2022-09-08  9:19               ` Greg KH
2022-09-08  9:19                 ` [Intel-gfx] " Greg KH
2022-09-08  9:19                 ` Greg KH
2022-09-08 11:59                 ` Zheng Hacker
2022-09-08 11:59                   ` [Intel-gfx] " Zheng Hacker
2022-09-16  6:39                   ` Zheng Hacker
2022-09-16  6:39                     ` [Intel-gfx] " Zheng Hacker
2022-09-16  6:39                     ` Zheng Hacker
2022-09-16  6:40                     ` Zheng Hacker
2022-09-16  6:40                       ` [Intel-gfx] " Zheng Hacker
2022-09-16  6:40                       ` Zheng Hacker
2022-09-16  8:25                     ` Greg KH
2022-09-16  8:25                       ` [Intel-gfx] " Greg KH
2022-09-16  8:25                       ` Greg KH
2022-09-16 15:21                       ` Zheng Hacker
2022-09-16 15:21                         ` [Intel-gfx] " Zheng Hacker
2022-09-16 15:21                         ` Zheng Hacker
2022-09-16 15:54                       ` Zheng Hacker
2022-09-16 15:54                         ` [Intel-gfx] " Zheng Hacker
2022-09-16 15:54                         ` Zheng Hacker
2022-09-17  9:08                         ` Greg KH
2022-09-17  9:08                           ` [Intel-gfx] " Greg KH
2022-09-17  9:08                           ` Greg KH
2022-09-17  9:10                           ` Zheng Hacker
2022-09-17  9:10                             ` [Intel-gfx] " Zheng Hacker
2022-09-18 17:08                           ` =?gb18030?B?s68=?=
2022-09-18 17:08                             ` [Intel-gfx] " =?gb18030?B?s68=?=
2022-09-18 17:17                           ` Zheng Hacker
2022-09-18 17:17                             ` [Intel-gfx] " Zheng Hacker
2022-09-18 17:17                             ` Zheng Hacker
2022-09-19 20:16   ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for " Patchwork
2022-09-06 12:58 ` Patchwork [this message]
2022-09-06 14:22   ` Zheng Hacker
2022-09-06 14:29   ` Zheng Hacker
2022-09-19 20:20 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for ✗ Fi.CI.BUILD: failure for drm/i915/gvt: fix double-free bug in split_2MB_gtt_entry. (rev3) 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=166246909164.8880.10585519190282207260@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=hackerzheng666@gmail.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.