From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for linux-next: build failure after merge of the drm-misc tree
Date: Mon, 16 Dec 2019 01:41:21 -0000 [thread overview]
Message-ID: <157646048164.5613.1862419248448095110@emeril.freedesktop.org> (raw)
In-Reply-To: <20191216122331.43c766f1@canb.auug.org.au>
== Series Details ==
Series: linux-next: build failure after merge of the drm-misc tree
URL : https://patchwork.freedesktop.org/series/70958/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
ccba0d4a341c linux-next: build failure after merge of the drm-misc tree
-:21: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 6aa192698089 ("drm/bridge: Add Analogix anx6345 support")'
#21:
6aa192698089 ("drm/bridge: Add Analogix anx6345 support")
-:47: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#47: FILE: drivers/gpu/drm/bridge/analogix/analogix-anx6345.c:739:
+ anx6345->i2c_clients[i] = i2c_new_dummy_device(client->adapter,
anx6345_i2c_addresses[i] >> 1);
total: 1 errors, 0 warnings, 1 checks, 16 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-12-16 1:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 1:23 linux-next: build failure after merge of the drm-misc tree Stephen Rothwell
2019-12-16 1:23 ` [Intel-gfx] " Stephen Rothwell
2019-12-16 1:23 ` Stephen Rothwell
2019-12-16 1:41 ` Patchwork [this message]
2019-12-16 2:02 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2019-12-16 3:43 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2019-12-17 13:19 ` Daniel Vetter
2019-12-17 13:19 ` [Intel-gfx] " Daniel Vetter
2019-12-17 13:19 ` Daniel Vetter
2019-12-17 20:22 ` Stephen Rothwell
2019-12-17 20:22 ` [Intel-gfx] " Stephen Rothwell
2019-12-17 20:22 ` Stephen Rothwell
2019-12-18 11:53 ` Daniel Vetter
2019-12-18 11:53 ` [Intel-gfx] " Daniel Vetter
2019-12-18 11:53 ` Daniel Vetter
2020-04-20 3:01 Stephen Rothwell
2020-04-29 10:11 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-06-17 0:59 Stephen Rothwell
2020-06-17 1:46 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-11-02 1:43 Stephen Rothwell
2020-11-02 1:59 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2021-10-15 9:26 Stephen Rothwell
2021-10-15 12:01 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2022-04-06 0:50 Stephen Rothwell
2022-04-06 3:01 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " 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=157646048164.5613.1862419248448095110@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=sfr@canb.auug.org.au \
/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.