All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, trix@redhat.com
Subject: RE: [RFC] MAINTAINERS tag for cleanup robot
Date: Sat, 21 Nov 2020 09:57:02 -0800 (PST)	[thread overview]
Message-ID: <5fb954ee.1c69fb81.2f993.e6ab@mx.google.com> (raw)
In-Reply-To: <20201121165058.1644182-1-trix@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1672 bytes --]

This is automated email and please do not reply to this email!

Dear submitter,

Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=388955

---Test result---

##############################
Test: CheckPatch - FAIL
Output:
MAINTAINERS tag for cleanup robot
WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#8: 
one or two fixes a release the use of 'treewide:' does not seem appropriate.

WARNING: From:/Signed-off-by: email name mismatch: 'From: "trix@redhat.com" <trix@redhat.com>' != 'Signed-off-by: Tom Rix <trix@redhat.com>'

total: 0 errors, 2 warnings, 61 lines checked

NOTE: For some of the reported defects, checkpatch may be able to
      mechanically convert to the typical style using --fix or --fix-inplace.

"[PATCH] MAINTAINERS tag for cleanup robot" has style problems, please review.

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.


##############################
Test: CheckGitLint - FAIL
Output:
MAINTAINERS tag for cleanup robot
12: B3 Line contains hard tab characters (\t): "	D: Commit subsystem prefix"
16: B3 Line contains hard tab characters (\t): "	D: fpga: dfl:"
24: B3 Line contains hard tab characters (\t): "	int v = 0;"
25: B3 Line contains hard tab characters (\t): "	FOO(a);"
33: B3 Line contains hard tab characters (\t): "	int v = 0;"
34: B3 Line contains hard tab characters (\t): "	FOO(a);"


##############################
Test: CheckBuildK - PASS



---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2020-11-21 17:57 UTC|newest]

Thread overview: 137+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-21 16:50 [RFC] MAINTAINERS tag for cleanup robot trix
2020-11-21 16:50 ` trix
2020-11-21 16:50 ` trix
2020-11-21 16:50 ` [Intel-gfx] " trix
2020-11-21 16:50 ` trix
2020-11-21 16:50 ` [Cluster-devel] " trix
2020-11-21 16:50 ` trix
2020-11-21 16:50 ` trix
2020-11-21 17:10 ` Joe Perches
2020-11-21 17:10   ` Joe Perches
2020-11-21 17:10   ` Joe Perches
2020-11-21 17:10   ` [Intel-gfx] " Joe Perches
2020-11-21 17:10   ` Joe Perches
2020-11-21 17:10   ` [Cluster-devel] " Joe Perches
2020-11-21 17:10   ` Joe Perches
2020-11-21 17:10   ` Joe Perches
2020-11-22 16:33   ` Tom Rix
2020-11-22 16:33     ` Tom Rix
2020-11-22 16:33     ` Tom Rix
2020-11-22 16:33     ` [Intel-gfx] " Tom Rix
2020-11-22 16:33     ` Tom Rix
2020-11-22 16:33     ` [Cluster-devel] " Tom Rix
2020-11-22 16:33     ` Tom Rix
2020-11-22 16:33     ` Tom Rix
2020-11-22 18:22     ` Joe Perches
2020-11-22 18:22       ` Joe Perches
2020-11-22 18:22       ` Joe Perches
2020-11-22 18:22       ` [Intel-gfx] " Joe Perches
2020-11-22 18:22       ` Joe Perches
2020-11-22 18:22       ` [Cluster-devel] " Joe Perches
2020-11-22 18:22       ` Joe Perches
2020-11-22 18:22       ` Joe Perches
2020-11-23 17:06       ` Tom Rix
2020-11-23 17:06         ` Tom Rix
2020-11-23 17:06         ` Tom Rix
2020-11-23 17:06         ` [Intel-gfx] " Tom Rix
2020-11-23 17:06         ` Tom Rix
2020-11-23 17:06         ` [Cluster-devel] " Tom Rix
2020-11-23 17:06         ` Tom Rix
2020-11-23 17:06         ` Tom Rix
2020-11-21 17:10 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-11-21 17:18 ` [RFC] " James Bottomley
2020-11-21 17:18   ` James Bottomley
2020-11-21 17:18   ` James Bottomley
2020-11-21 17:18   ` [Intel-gfx] " James Bottomley
2020-11-21 17:18   ` James Bottomley
2020-11-21 17:18   ` [Cluster-devel] " James Bottomley
2020-11-21 17:18   ` James Bottomley
2020-11-21 17:18   ` James Bottomley
2020-11-21 18:02   ` Joe Perches
2020-11-21 18:02     ` Joe Perches
2020-11-21 18:02     ` Joe Perches
2020-11-21 18:02     ` [Intel-gfx] " Joe Perches
2020-11-21 18:02     ` Joe Perches
2020-11-21 18:02     ` [Cluster-devel] " Joe Perches
2020-11-21 18:02     ` Joe Perches
2020-11-21 18:02     ` Joe Perches
2020-11-23  5:20     ` Joe Perches
2020-11-23 15:52   ` Jani Nikula
2020-11-23 15:52     ` Jani Nikula
2020-11-23 15:52     ` Jani Nikula
2020-11-23 15:52     ` [Intel-gfx] " Jani Nikula
2020-11-23 15:52     ` Jani Nikula
2020-11-23 15:52     ` [Cluster-devel] " Jani Nikula
2020-11-23 15:52     ` Jani Nikula
2020-11-23 16:17     ` Lukas Bulwahn
2020-11-23 16:17       ` Lukas Bulwahn
2020-11-23 16:17       ` Lukas Bulwahn
2020-11-23 16:17       ` [Intel-gfx] " Lukas Bulwahn
2020-11-23 16:17       ` Lukas Bulwahn
2020-11-23 16:17       ` [Cluster-devel] " Lukas Bulwahn
2020-11-23 16:17       ` Lukas Bulwahn
2020-11-23 16:17       ` Lukas Bulwahn
2020-11-21 17:39 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-11-21 17:57 ` bluez.test.bot [this message]
2020-11-21 18:47 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-11-22  3:23 ` [RFC] " Matthew Wilcox
2020-11-22  3:23   ` Matthew Wilcox
2020-11-22  3:23   ` [Intel-gfx] " Matthew Wilcox
2020-11-22  3:23   ` Matthew Wilcox
2020-11-22  3:23   ` [Cluster-devel] " Matthew Wilcox
2020-11-22  3:23   ` Matthew Wilcox
2020-11-22  3:23   ` Matthew Wilcox
2020-11-22 14:46   ` Tom Rix
2020-11-22 14:46     ` Tom Rix
2020-11-22 14:46     ` Tom Rix
2020-11-22 14:46     ` [Intel-gfx] " Tom Rix
2020-11-22 14:46     ` Tom Rix
2020-11-22 14:46     ` [Cluster-devel] " Tom Rix
2020-11-22 14:46     ` Tom Rix
2020-11-22 14:46     ` Tom Rix
2020-11-22 14:56     ` Matthew Wilcox
2020-11-22 14:56       ` Matthew Wilcox
2020-11-22 14:56       ` [Intel-gfx] " Matthew Wilcox
2020-11-22 14:56       ` Matthew Wilcox
2020-11-22 14:56       ` [Cluster-devel] " Matthew Wilcox
2020-11-22 14:56       ` Matthew Wilcox
2020-11-22 14:56       ` Matthew Wilcox
2020-11-22 16:10       ` Tom Rix
2020-11-22 16:10         ` Tom Rix
2020-11-22 16:10         ` Tom Rix
2020-11-22 16:10         ` [Intel-gfx] " Tom Rix
2020-11-22 16:10         ` Tom Rix
2020-11-22 16:10         ` [Cluster-devel] " Tom Rix
2020-11-22 16:10         ` Tom Rix
2020-11-22 16:10         ` Tom Rix
2020-11-22 16:49         ` James Bottomley
2020-11-22 16:49           ` James Bottomley
2020-11-22 16:49           ` James Bottomley
2020-11-22 16:49           ` [Intel-gfx] " James Bottomley
2020-11-22 16:49           ` James Bottomley
2020-11-22 16:49           ` [Cluster-devel] " James Bottomley
2020-11-22 16:49           ` James Bottomley
2020-11-22 16:49           ` James Bottomley
2020-11-22 18:23           ` Joe Perches
2020-11-22 18:23             ` Joe Perches
2020-11-22 18:23             ` Joe Perches
2020-11-22 18:23             ` [Intel-gfx] " Joe Perches
2020-11-22 18:23             ` Joe Perches
2020-11-22 18:23             ` [Cluster-devel] " Joe Perches
2020-11-22 18:23             ` Joe Perches
2020-11-22 18:23             ` Joe Perches
2020-11-22 22:33             ` Finn Thain
2020-11-22 22:33               ` Finn Thain
2020-11-22 22:33               ` [Intel-gfx] " Finn Thain
2020-11-22 22:33               ` Finn Thain
2020-11-22 22:33               ` [Cluster-devel] " Finn Thain
2020-11-22 22:33               ` Finn Thain
2020-11-22 22:33               ` Finn Thain
2020-11-23  0:53               ` Joe Perches
2020-11-23  0:53                 ` Joe Perches
2020-11-23  0:53                 ` Joe Perches
2020-11-23  0:53                 ` [Intel-gfx] " Joe Perches
2020-11-23  0:53                 ` Joe Perches
2020-11-23  0:53                 ` [Cluster-devel] " Joe Perches
2020-11-23  0:53                 ` Joe Perches
2020-11-23  0:53                 ` Joe Perches

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=5fb954ee.1c69fb81.2f993.e6ab@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=trix@redhat.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.