From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [1/2] Bluetooth: Fix not sending Set Extended Scan Response
Date: Sun, 15 Nov 2020 10:51:27 -0800 (PST) [thread overview]
Message-ID: <5fb178af.1c69fb81.26650.ae6e@mx.google.com> (raw)
In-Reply-To: <20201114004434.3852104-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1086 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=384043
---Test result---
##############################
Test: CheckPatch - FAIL
Output:
workflow: Add workflow files for ci
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#18:
new file mode 100644
ERROR: Missing Signed-off-by: line(s)
total: 1 errors, 1 warnings, 49 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] workflow: Add workflow files for ci" 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 - PASS
##############################
Test: CheckBuildK - PASS
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2020-11-15 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-14 0:44 [PATCH 1/2] Bluetooth: Fix not sending Set Extended Scan Response Luiz Augusto von Dentz
2020-11-14 0:44 ` [PATCH 2/2] Bluetooth: Rename get_adv_instance_scan_rsp Luiz Augusto von Dentz
2020-11-23 12:00 ` Marcel Holtmann
2020-11-15 18:51 ` bluez.test.bot [this message]
2020-11-23 12:01 ` [PATCH 1/2] Bluetooth: Fix not sending Set Extended Scan Response Marcel Holtmann
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=5fb178af.1c69fb81.26650.ae6e@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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;
as well as URLs for NNTP newsgroup(s).