From: Patchwork <patchwork@emeril.freedesktop.org>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for drm/i915/cfl: Adding another PCI Device ID. (rev2)
Date: Sat, 02 Feb 2019 00:02:20 -0000 [thread overview]
Message-ID: <20190202000220.681.32884@emeril.freedesktop.org> (raw)
In-Reply-To: <20190201053844.12914-1-rodrigo.vivi@intel.com>
== Series Details ==
Series: drm/i915/cfl: Adding another PCI Device ID. (rev2)
URL : https://patchwork.freedesktop.org/series/56075/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
d78761758c42 drm/i915/cfl: Adding another PCI Device ID.
-:15: WARNING:BAD_SIGN_OFF: email address 'Dmitry Rogozhkin<dmitry.v.rogozhkin@intel.com>' might be better as 'Dmitry Rogozhkin <dmitry.v.rogozhkin@intel.com>'
#15:
Reported-by: Dmitry Rogozhkin<dmitry.v.rogozhkin@intel.com>
-:16: WARNING:BAD_SIGN_OFF: email address 'Dmitry Rogozhkin<dmitry.v.rogozhkin@intel.com>' might be better as 'Dmitry Rogozhkin <dmitry.v.rogozhkin@intel.com>'
#16:
Cc: Dmitry Rogozhkin<dmitry.v.rogozhkin@intel.com>
total: 0 errors, 2 warnings, 0 checks, 23 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:[~2019-02-02 0:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 5:38 [PATCH] drm/i915/cfl: Adding another PCI Device ID Rodrigo Vivi
2019-02-01 6:15 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-02-01 6:36 ` ✓ Fi.CI.BAT: success " Patchwork
2019-02-01 9:42 ` ✓ Fi.CI.IGT: " Patchwork
2019-02-01 18:01 ` [PATCH] " Souza, Jose
2019-02-01 23:50 ` Rodrigo Vivi
2019-02-02 0:09 ` Souza, Jose
2019-02-02 8:23 ` Rodrigo Vivi
2019-02-02 0:02 ` Patchwork [this message]
2019-02-02 0:24 ` ✓ Fi.CI.BAT: success for drm/i915/cfl: Adding another PCI Device ID. (rev2) Patchwork
2019-02-02 1:30 ` ✓ Fi.CI.IGT: " 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=20190202000220.681.32884@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox