All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Arunpravin" <arunpravin.paneerselvam@amd.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [v11,1/5] drm: improve drm_buddy_alloc function
Date: Thu, 27 Jan 2022 16:23:14 -0000	[thread overview]
Message-ID: <164330059475.23659.11052618961942719157@emeril.freedesktop.org> (raw)
In-Reply-To: <20220127141107.173692-1-Arunpravin.PaneerSelvam@amd.com>

[-- Attachment #1: Type: text/plain, Size: 2758 bytes --]

== Series Details ==

Series: series starting with [v11,1/5] drm: improve drm_buddy_alloc function
URL   : https://patchwork.freedesktop.org/series/99430/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_11151 -> Patchwork_22128
====================================================

Summary
-------

  **SUCCESS**

  No regressions found.

  External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22128/index.html

Participating hosts (46 -> 39)
------------------------------

  Missing    (7): bat-adls-5 fi-hsw-4200u fi-bsw-cyan fi-ctg-p8600 fi-kbl-8809g fi-pnv-d510 fi-bdw-samus 

Known issues
------------

  Here are the changes found in Patchwork_22128 that come from known issues:

### IGT changes ###

#### Issues hit ####

  * igt@kms_psr@primary_page_flip:
    - fi-skl-6600u:       [PASS][1] -> [FAIL][2] ([i915#4547])
   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11151/fi-skl-6600u/igt@kms_psr@primary_page_flip.html
   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22128/fi-skl-6600u/igt@kms_psr@primary_page_flip.html

  * igt@runner@aborted:
    - fi-skl-6600u:       NOTRUN -> [FAIL][3] ([i915#4312])
   [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22128/fi-skl-6600u/igt@runner@aborted.html

  
#### Warnings ####

  * igt@i915_selftest@live@hangcheck:
    - bat-dg1-5:          [DMESG-FAIL][4] ([i915#4957]) -> [DMESG-FAIL][5] ([i915#4494] / [i915#4957])
   [4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11151/bat-dg1-5/igt@i915_selftest@live@hangcheck.html
   [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22128/bat-dg1-5/igt@i915_selftest@live@hangcheck.html

  
  [i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
  [i915#4494]: https://gitlab.freedesktop.org/drm/intel/issues/4494
  [i915#4547]: https://gitlab.freedesktop.org/drm/intel/issues/4547
  [i915#4957]: https://gitlab.freedesktop.org/drm/intel/issues/4957


Build changes
-------------

  * Linux: CI_DRM_11151 -> Patchwork_22128

  CI-20190529: 20190529
  CI_DRM_11151: 627e2885b51ab503a98aa89f0a0bd68416c731fc @ git://anongit.freedesktop.org/gfx-ci/linux
  IGT_6336: ae2eb9e18bc58a4c45f28cfd80962938198dec3c @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
  Patchwork_22128: a629aca723cdab39652e834b30f0513757f78441 @ git://anongit.freedesktop.org/gfx-ci/linux


== Linux commits ==

a629aca723cd drm/amdgpu: add drm buddy support to amdgpu
f26779496cc3 drm/amdgpu: move vram inline functions into a header
957142d57613 drm: implement a method to free unused pages
50185f5f7e57 drm: implement top-down allocation method
00470383ca08 drm: improve drm_buddy_alloc function

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22128/index.html

[-- Attachment #2: Type: text/html, Size: 3500 bytes --]

  parent reply	other threads:[~2022-01-27 16:23 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 14:11 [PATCH v11 1/5] drm: improve drm_buddy_alloc function Arunpravin
2022-01-27 14:11 ` Arunpravin
2022-01-27 14:11 ` [Intel-gfx] " Arunpravin
2022-01-27 14:11 ` [PATCH v11 2/5] drm: implement top-down allocation method Arunpravin
2022-01-27 14:11   ` Arunpravin
2022-01-27 14:11   ` [Intel-gfx] " Arunpravin
2022-01-27 14:11 ` [PATCH v11 3/5] drm: implement a method to free unused pages Arunpravin
2022-01-27 14:11   ` Arunpravin
2022-01-27 14:11   ` [Intel-gfx] " Arunpravin
2022-01-27 14:11 ` [PATCH v11 4/5] drm/amdgpu: move vram inline functions into a header Arunpravin
2022-01-27 14:11   ` Arunpravin
2022-01-27 14:11   ` [Intel-gfx] " Arunpravin
2022-01-27 14:11 ` [PATCH v11 5/5] drm/amdgpu: add drm buddy support to amdgpu Arunpravin
2022-01-27 14:11   ` Arunpravin
2022-01-27 14:11   ` [Intel-gfx] " Arunpravin
2022-01-28 14:18   ` Matthew Auld
2022-01-28 14:18     ` [Intel-gfx] " Matthew Auld
2022-02-04 11:22     ` Arunpravin
2022-02-04 11:22       ` [Intel-gfx] " Arunpravin
2022-02-04 13:23       ` Christian König
2022-02-04 13:23         ` [Intel-gfx] " Christian König
2022-02-08 11:20         ` Arunpravin
2022-02-08 11:20           ` [Intel-gfx] " Arunpravin
2022-02-10 17:52           ` Matthew Auld
2022-02-10 17:52             ` [Intel-gfx] " Matthew Auld
2022-01-27 15:52 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v11,1/5] drm: improve drm_buddy_alloc function Patchwork
2022-01-27 16:23 ` Patchwork [this message]
2022-01-27 21:45 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2022-02-10 16:10 ` [PATCH v11 1/5] " Matthew Auld
2022-02-10 16:10   ` Matthew Auld
2022-02-10 16:10   ` [Intel-gfx] " Matthew Auld
2022-02-11  9:27   ` Arunpravin
2022-02-11  9:27     ` Arunpravin
2022-02-11  9:27     ` [Intel-gfx] " Arunpravin

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=164330059475.23659.11052618961942719157@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=arunpravin.paneerselvam@amd.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.