From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, dhowells@redhat.com
Subject: RE: [RFC,1/3] net: Drop the size argument from ->sendmsg()
Date: Wed, 22 Mar 2023 18:11:27 -0700 (PDT) [thread overview]
Message-ID: <641ba73f.170a0220.ebdc2.62e2@mx.google.com> (raw)
In-Reply-To: <20230322135612.3265850-2-dhowells@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 3205 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=732753
---Test result---
Test Summary:
CheckPatch FAIL 18.11 seconds
GitLint PASS 0.26 seconds
SubjectPrefix FAIL 0.40 seconds
BuildKernel PASS 31.50 seconds
CheckAllWarning PASS 34.46 seconds
CheckSparse WARNING 39.28 seconds
CheckSmatch WARNING 108.13 seconds
BuildKernel32 PASS 30.32 seconds
TestRunnerSetup PASS 433.80 seconds
TestRunner_l2cap-tester PASS 15.85 seconds
TestRunner_iso-tester PASS 15.61 seconds
TestRunner_bnep-tester PASS 5.07 seconds
TestRunner_mgmt-tester PASS 103.41 seconds
TestRunner_rfcomm-tester PASS 8.14 seconds
TestRunner_sco-tester PASS 7.43 seconds
TestRunner_ioctl-tester PASS 8.59 seconds
TestRunner_mesh-tester PASS 6.36 seconds
TestRunner_smp-tester PASS 7.37 seconds
TestRunner_userchan-tester PASS 5.26 seconds
IncrementalBuild PASS 28.86 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[RFC,1/3] net: Drop the size argument from ->sendmsg()
WARNING: Unnecessary space before function pointer arguments
#729: FILE: include/linux/net.h:195:
+ int (*sendmsg) (struct socket *sock, struct msghdr *m);
WARNING: function definition argument 'struct rxrpc_sock *' should also have an identifier name
#2195: FILE: net/rxrpc/ar-internal.h:1224:
+int rxrpc_do_sendmsg(struct rxrpc_sock *, struct msghdr *);
WARNING: function definition argument 'struct msghdr *' should also have an identifier name
#2195: FILE: net/rxrpc/ar-internal.h:1224:
+int rxrpc_do_sendmsg(struct rxrpc_sock *, struct msghdr *);
total: 0 errors, 3 warnings, 2169 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.
/github/workspace/src/src/13184097.patch has style problems, please review.
NOTE: Ignored message types: UNKNOWN_COMMIT_ID
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/sco.c: note: in included file:./include/net/bluetooth/hci_core.h:148:35: warning: array of flexible structures
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
net/bluetooth/sco.c: note: in included file:./include/net/bluetooth/hci_core.h:148:35: warning: array of flexible structures
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2023-03-23 1:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6419bda5a2b4d_59e87208ca@willemb.c.googlers.com.notmuch>
[not found] ` <20230322135612.3265850-1-dhowells@redhat.com>
2023-03-22 13:56 ` [RFC PATCH 1/3] net: Drop the size argument from ->sendmsg() David Howells
2023-03-22 14:13 ` [RFC,1/3] " bluez.test.bot
2023-03-23 1:11 ` bluez.test.bot [this message]
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=641ba73f.170a0220.ebdc2.62e2@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=dhowells@redhat.com \
--cc=linux-bluetooth@vger.kernel.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