From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, reoshiseki@gmail.com
Subject: RE: include/net/bluetooth/mgmt.h: fix typo in struct name
Date: Fri, 20 Nov 2020 17:32:22 -0800 (PST) [thread overview]
Message-ID: <5fb86e26.1c69fb81.5f9ba.6a19@mx.google.com> (raw)
In-Reply-To: <20201119071038.380502-1-reoshiseki@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1197 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=387293
---Test result---
##############################
Test: CheckPatch - FAIL
Output:
include/net/bluetooth/mgmt.h: fix typo in struct name
WARNING: Missing commit description - Add an appropriate one
WARNING: From:/Signed-off-by: email name mismatch: 'From: Reo Shiseki <reoshiseki@gmail.com>' != 'Signed-off-by: n01e0 <reoshiseki@gmail.com>'
total: 0 errors, 2 warnings, 0 checks, 32 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] include/net/bluetooth/mgmt.h: fix typo in struct name" 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-21 1:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 7:10 [PATCH] include/net/bluetooth/mgmt.h: fix typo in struct name n01e0
2020-11-21 1:32 ` bluez.test.bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-19 7:28 n01e0
2020-11-21 1:32 ` bluez.test.bot
2020-11-19 7:37 [PATCH] " n01e0
2020-11-21 1:33 ` bluez.test.bot
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=5fb86e26.1c69fb81.5f9ba.6a19@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=reoshiseki@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