All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Mauro Carvalho Chehab" <mchehab@kernel.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Move TLB invalidation code for its own file and document it (rev3)
Date: Mon, 01 Aug 2022 19:56:06 -0000	[thread overview]
Message-ID: <165938376621.14741.12804653238875274626@emeril.freedesktop.org> (raw)
In-Reply-To: <cover.1659077372.git.mchehab@kernel.org>

== Series Details ==

Series: Move TLB invalidation code for its own file and document it (rev3)
URL   : https://patchwork.freedesktop.org/series/106805/
State : warning

== Summary ==

Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.



  parent reply	other threads:[~2022-08-01 19:56 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-29  7:03 [PATCH v2 0/2] Move TLB invalidation code for its own file and document it Mauro Carvalho Chehab
2022-07-29  7:03 ` [Intel-gfx] " Mauro Carvalho Chehab
2022-07-29  7:03 ` Mauro Carvalho Chehab
2022-07-29  7:03 ` [PATCH v2 1/2] drm/i915/gt: Move TLB invalidation to its own file Mauro Carvalho Chehab
2022-07-29  7:03   ` [Intel-gfx] " Mauro Carvalho Chehab
2022-07-29  7:03   ` Mauro Carvalho Chehab
2022-08-02 22:21   ` [Intel-gfx] " Niranjana Vishwanathapura
2022-08-02 22:21     ` Niranjana Vishwanathapura
2022-08-03  9:19   ` Andi Shyti
2022-08-03  9:19     ` [Intel-gfx] " Andi Shyti
2022-08-03  9:19     ` Andi Shyti
2022-07-29  7:03 ` [PATCH v2 2/2] drm/i915/gt: document TLB cache invalidation functions Mauro Carvalho Chehab
2022-07-29  7:03   ` [Intel-gfx] " Mauro Carvalho Chehab
2022-07-29  7:03   ` Mauro Carvalho Chehab
2022-08-02 22:30   ` [Intel-gfx] " Niranjana Vishwanathapura
2022-08-02 22:30     ` Niranjana Vishwanathapura
2022-08-02 22:30     ` Niranjana Vishwanathapura
2022-08-04  7:24     ` Mauro Carvalho Chehab
2022-08-04  7:24       ` Mauro Carvalho Chehab
2022-08-04  7:24       ` Mauro Carvalho Chehab
2022-07-29  7:14 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Move TLB invalidation code for its own file and document it (rev2) Patchwork
2022-08-01 19:56 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Move TLB invalidation code for its own file and document it (rev3) Patchwork
2022-08-01 19:56 ` Patchwork [this message]
2022-08-01 20:23 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-08-02  5:46 ` [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=165938376621.14741.12804653238875274626@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mchehab@kernel.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.