From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Michal Wajdeczko" <michal.wajdeczko@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/guc: Keep strict GuC ABI definitions separate
Date: Sat, 20 Feb 2021 13:09:30 -0000 [thread overview]
Message-ID: <161382657030.24212.6478440504036298015@emeril.freedesktop.org> (raw)
In-Reply-To: <20210220124443.1920-1-michal.wajdeczko@intel.com>
== Series Details ==
Series: drm/i915/guc: Keep strict GuC ABI definitions separate
URL : https://patchwork.freedesktop.org/series/87256/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
1e8af930db8a drm/i915/guc: Keep strict GuC ABI definitions separate
-:16: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#16:
new file mode 100644
total: 0 errors, 1 warnings, 0 checks, 601 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-02-20 13:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-20 12:44 [Intel-gfx] [PATCH] drm/i915/guc: Keep strict GuC ABI definitions separate Michal Wajdeczko
2021-02-20 13:09 ` Patchwork [this message]
2021-02-20 13:40 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2021-02-20 15:35 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/guc: Keep strict GuC ABI definitions separate (rev2) Patchwork
2021-02-20 16:04 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-02-20 17:30 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-02-24 19:52 ` [Intel-gfx] [PATCH] drm/i915/guc: Keep strict GuC ABI definitions separate Michał Winiarski
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=161382657030.24212.6478440504036298015@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michal.wajdeczko@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.