From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Tvrtko Ursulin" <tvrtko.ursulin@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Stop propagating fence errors by default
Date: Fri, 07 May 2021 09:29:39 -0000 [thread overview]
Message-ID: <162037977934.10707.18345031126344088595@emeril.freedesktop.org> (raw)
In-Reply-To: <20210507083521.2406201-1-tvrtko.ursulin@linux.intel.com>
== Series Details ==
Series: drm/i915: Stop propagating fence errors by default
URL : https://patchwork.freedesktop.org/series/89857/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
615d0d0d9d9f drm/i915: Stop propagating fence errors by default
-:22: ERROR:BAD_SIGN_OFF: Unrecognized email address: 'Miroslav Bendik'
#22:
Reported-by: Miroslav Bendik
total: 1 errors, 0 warnings, 0 checks, 59 lines checked
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-05-07 9:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 8:35 [PATCH] drm/i915: Stop propagating fence errors by default Tvrtko Ursulin
2021-05-07 8:35 ` [Intel-gfx] " Tvrtko Ursulin
2021-05-07 9:29 ` Patchwork [this message]
2021-05-07 9:58 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-05-07 11:38 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-05-10 1:36 ` [Intel-gfx] [PATCH] " Jason Ekstrand
2021-05-10 1:36 ` Jason Ekstrand
2021-05-10 15:55 ` Daniel Vetter
2021-05-10 15:55 ` [Intel-gfx] " Daniel Vetter
2021-05-11 9:05 ` Tvrtko Ursulin
2021-05-11 9:05 ` [Intel-gfx] " Tvrtko Ursulin
2021-05-17 15:12 ` Daniel Vetter
2021-05-17 15:12 ` [Intel-gfx] " Daniel Vetter
2021-05-17 15:33 ` Tvrtko Ursulin
2021-05-17 15:33 ` [Intel-gfx] " Tvrtko Ursulin
2021-05-17 15:51 ` Daniel Vetter
2021-05-17 15:51 ` [Intel-gfx] " Daniel Vetter
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=162037977934.10707.18345031126344088595@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tvrtko.ursulin@linux.intel.com \
/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.