All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Jani Nikula" <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/6] relay: allow the use of const callback structs
Date: Wed, 18 Nov 2020 18:43:53 -0000	[thread overview]
Message-ID: <160572503329.24804.9208919784952794537@emeril.freedesktop.org> (raw)
In-Reply-To: <20201118165320.26829-1-jani.nikula@intel.com>

== Series Details ==

Series: series starting with [1/6] relay: allow the use of const callback structs
URL   : https://patchwork.freedesktop.org/series/84030/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
76e9bf02701b relay: allow the use of const callback structs
-:235: WARNING:SYMBOLIC_PERMS: Symbolic permissions 'S_IRUSR' are not preferred. Consider using octal permissions '0400'.
#235: FILE: kernel/relay.c:439:
+				    S_IRUSR, buf, &chan->is_global);

-:247: WARNING:SYMBOLIC_PERMS: Symbolic permissions 'S_IRUSR' are not preferred. Consider using octal permissions '0400'.
#247: FILE: kernel/relay.c:473:
+					    S_IRUSR, buf, &chan->is_global);

total: 0 errors, 2 warnings, 0 checks, 267 lines checked
25fce26c36a2 drm/i915: make relay callbacks const
e087a43fd799 ath10k: make relay callbacks const
bd0a1edfcd78 ath11k: make relay callbacks const
ae80849da1c9 ath9k: make relay callbacks const
ac95f490fbc0 blktrace: make relay callbacks const


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

  parent reply	other threads:[~2020-11-18 18:43 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-18 16:53 [PATCH 1/6] relay: allow the use of const callback structs Jani Nikula
2020-11-18 16:53 ` [Intel-gfx] " Jani Nikula
2020-11-18 16:53 ` Jani Nikula
2020-11-18 16:53 ` Jani Nikula
2020-11-18 16:53 ` [PATCH 2/6] drm/i915: make relay callbacks const Jani Nikula
2020-11-18 16:53   ` [Intel-gfx] " Jani Nikula
2020-11-18 16:53 ` [PATCH 3/6] ath10k: " Jani Nikula
2020-11-18 16:53   ` [Intel-gfx] " Jani Nikula
2020-11-18 16:53   ` Jani Nikula
2020-11-18 17:13   ` Kalle Valo
2020-11-18 17:13     ` [Intel-gfx] " Kalle Valo
2020-11-18 17:13     ` Kalle Valo
2020-11-18 16:53 ` [PATCH 4/6] ath11k: " Jani Nikula
2020-11-18 16:53   ` [Intel-gfx] " Jani Nikula
2020-11-18 16:53   ` Jani Nikula
2020-11-19  9:31   ` Jani Nikula
2020-11-19  9:31     ` [Intel-gfx] " Jani Nikula
2020-11-19  9:31     ` Jani Nikula
2020-11-19 11:40     ` Kalle Valo
2020-11-19 11:40       ` [Intel-gfx] " Kalle Valo
2020-11-19 11:40       ` Kalle Valo
2020-11-18 16:53 ` [PATCH 5/6] ath9k: " Jani Nikula
2020-11-18 16:53   ` [Intel-gfx] " Jani Nikula
2020-11-18 17:03   ` Kalle Valo
2020-11-18 17:03     ` [Intel-gfx] " Kalle Valo
2020-11-18 17:15     ` Kalle Valo
2020-11-18 17:15       ` [Intel-gfx] " Kalle Valo
2020-11-18 16:53 ` [PATCH 6/6] blktrace: " Jani Nikula
2020-11-18 16:53   ` [Intel-gfx] " Jani Nikula
2020-11-18 18:43 ` Patchwork [this message]
2020-11-18 18:45 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/6] relay: allow the use of const callback structs Patchwork
2020-11-18 19:13 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-11-19  4:08 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-11-19  8:11 ` [PATCH 1/6] " Christoph Hellwig
2020-11-19  8:11   ` [Intel-gfx] " Christoph Hellwig
2020-11-19  8:11   ` Christoph Hellwig
2020-11-19  8:11   ` Christoph Hellwig
2020-11-19  8:11   ` Christoph Hellwig
2020-11-19  8:11     ` [Intel-gfx] " Christoph Hellwig
2020-11-19  8:11     ` Christoph Hellwig
2020-11-19  8:11     ` Christoph Hellwig
2020-11-23 18:01   ` Jani Nikula
2020-11-23 18:01     ` [Intel-gfx] " Jani Nikula
2020-11-23 18:01     ` Jani Nikula
2020-11-23 18:01     ` Jani Nikula

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=160572503329.24804.9208919784952794537@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@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.