public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/4] component: Add documentation
Date: Thu, 07 Feb 2019 23:41:54 -0000	[thread overview]
Message-ID: <20190207234154.724.60289@emeril.freedesktop.org> (raw)
In-Reply-To: <20190207232759.14553-1-daniel.vetter@ffwll.ch>

== Series Details ==

Series: series starting with [1/4] component: Add documentation
URL   : https://patchwork.freedesktop.org/series/56372/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
4b25d63c44e7 component: Add documentation
-:27: WARNING:TYPO_SPELLING: 'superflous' may be misspelled - perhaps 'superfluous'?
#27: 
v4: Remove a few superflous "This".

-:41: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#41: 
new file mode 100644

-:46: WARNING:SPDX_LICENSE_TAG: Missing or malformed SPDX-License-Identifier tag in line 1
#46: FILE: Documentation/driver-api/component.rst:1:
+======================================

-:264: CHECK:LINE_SPACING: Please don't use multiple blank lines
#264: FILE: include/linux/component.h:7:
 
+

-:357: WARNING:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch author 'Daniel Vetter <daniel.vetter@ffwll.ch>'

total: 0 errors, 4 warnings, 1 checks, 283 lines checked
7648f41d42d8 components: multiple components for a device
-:44: WARNING:FUNCTION_ARGUMENTS: function definition argument 'struct device *' should also have an identifier name
#44: FILE: drivers/base/component.c:50:
+	int (*compare_typed)(struct device *, int, void *);

-:44: WARNING:FUNCTION_ARGUMENTS: function definition argument 'int' should also have an identifier name
#44: FILE: drivers/base/component.c:50:
+	int (*compare_typed)(struct device *, int, void *);

-:44: WARNING:FUNCTION_ARGUMENTS: function definition argument 'void *' should also have an identifier name
#44: FILE: drivers/base/component.c:50:
+	int (*compare_typed)(struct device *, int, void *);

-:112: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#112: FILE: drivers/base/component.c:337:
+static void __component_match_add(struct device *master,
 	struct component_match **matchptr,

-:153: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#153: FILE: drivers/base/component.c:401:
+void component_match_add_release(struct device *master,
+	struct component_match **matchptr,

-:180: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#180: FILE: drivers/base/component.c:428:
+void component_match_add_typed(struct device *master,
+	struct component_match **matchptr,

-:209: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#209: FILE: drivers/base/component.c:665:
+static int __component_add(struct device *dev, const struct component_ops *ops,
+	int subcomponent)

-:237: WARNING:TYPO_SPELLING: 'registerd' may be misspelled - perhaps 'registered'?
#237: FILE: drivers/base/component.c:707:
+ * components registerd on the same device @dev. These components are match

-:246: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#246: FILE: drivers/base/component.c:716:
+int component_add_typed(struct device *dev, const struct component_ops *ops,
+	int subcomponent)

-:286: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#286: FILE: include/linux/component.h:38:
+int component_add_typed(struct device *dev, const struct component_ops *ops,
+	int subcomponent);

-:295: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#295: FILE: include/linux/component.h:97:
+void component_match_add_typed(struct device *master,
+	struct component_match **matchptr,

total: 0 errors, 4 warnings, 7 checks, 259 lines checked
c583a70a9f8d drm/doc: document recommended component helper usage
-:17: WARNING:SPDX_LICENSE_TAG: Missing or malformed SPDX-License-Identifier tag in line 1
#17: FILE: Documentation/driver-api/component.rst:1:
+.. _component:

-:62: WARNING:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch author 'Daniel Vetter <daniel.vetter@ffwll.ch>'

total: 0 errors, 2 warnings, 0 checks, 36 lines checked
cf66b4cc035d i915/snd_hdac: I915 subcomponent for the snd_hdac
-:16: WARNING:BAD_SIGN_OFF: Non-standard signature: Signed-off-by-by:
#16: 
Signed-off-by-by: Ramalingam C <ramalinagm.c@intel.com> (commit message)

total: 0 errors, 1 warnings, 0 checks, 66 lines checked

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-02-07 23:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-07 23:27 [PATCH 1/4] component: Add documentation Daniel Vetter
2019-02-07 23:27 ` [PATCH 2/4] components: multiple components for a device Daniel Vetter
2019-02-07 23:30   ` Rafael J. Wysocki
2019-02-08 10:28   ` Russell King - ARM Linux admin
2019-02-08 15:23     ` Daniel Vetter
2019-02-08 15:36       ` Daniel Vetter
2019-02-08 11:52   ` Greg Kroah-Hartman
2019-02-07 23:27 ` [PATCH 3/4] drm/doc: document recommended component helper usage Daniel Vetter
2019-02-07 23:27 ` [PATCH 4/4] i915/snd_hdac: I915 subcomponent for the snd_hdac Daniel Vetter
2019-02-07 23:41 ` Patchwork [this message]
2019-02-08  0:00 ` ✓ Fi.CI.BAT: success for series starting with [1/4] component: Add documentation Patchwork
2019-02-08  4:08 ` ✓ Fi.CI.IGT: " Patchwork
2019-02-08 11:51 ` [PATCH 1/4] " Greg Kroah-Hartman
2019-02-08 15:29   ` Daniel Vetter
2019-02-08 15:45     ` Daniel Vetter
2019-02-18  3:31 ` Randy Dunlap

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=20190207234154.724.60289@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox