From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, kuba@kernel.org
Subject: RE: bluetooth: don't write directly to netdev->dev_addr
Date: Fri, 22 Oct 2021 11:11:10 -0700 (PDT) [thread overview]
Message-ID: <6172febe.1c69fb81.1da30.99a9@mx.google.com> (raw)
In-Reply-To: <20211022174232.2510917-2-kuba@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2172 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=568737
---Test result---
Test Summary:
CheckPatch PASS 1.38 seconds
GitLint PASS 0.72 seconds
BuildKernel FAIL 533.55 seconds
TestRunner: Setup PASS 424.84 seconds
TestRunner: l2cap-tester PASS 8.46 seconds
TestRunner: bnep-tester PASS 4.73 seconds
TestRunner: mgmt-tester PASS 43.03 seconds
TestRunner: rfcomm-tester PASS 5.60 seconds
TestRunner: sco-tester PASS 6.05 seconds
TestRunner: smp-tester PASS 5.72 seconds
TestRunner: userchan-tester PASS 4.91 seconds
Details
##############################
Test: BuildKernel - FAIL - 533.55 seconds
Build Kernel with minimal configuration supports Bluetooth
net/bluetooth/6lowpan.c: In function ‘setup_netdev’:
net/bluetooth/6lowpan.c:677:25: error: passing argument 2 of ‘__dev_addr_set’ from incompatible pointer type [-Werror=incompatible-pointer-types]
677 | __dev_addr_set(netdev, &addr, sizeof(addr));
| ^~~~~
| |
| bdaddr_t * {aka struct <anonymous> *}
In file included from ./include/uapi/linux/if_arp.h:27,
from ./include/linux/if_arp.h:23,
from net/bluetooth/6lowpan.c:7:
./include/linux/netdevice.h:4645:50: note: expected ‘const u8 *’ {aka ‘const unsigned char *’} but argument is of type ‘bdaddr_t *’ {aka ‘struct <anonymous> *’}
4645 | __dev_addr_set(struct net_device *dev, const u8 *addr, size_t len)
| ~~~~~~~~~~^~~~
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:277: net/bluetooth/6lowpan.o] Error 1
make[1]: *** [scripts/Makefile.build:540: net/bluetooth] Error 2
make: *** [Makefile:1868: net] Error 2
---
Regards,
Linux Bluetooth
[-- Attachment #2: l2cap-tester.log --]
[-- Type: application/octet-stream, Size: 44357 bytes --]
[-- Attachment #3: bnep-tester.log --]
[-- Type: application/octet-stream, Size: 3564 bytes --]
[-- Attachment #4: mgmt-tester.log --]
[-- Type: application/octet-stream, Size: 353167 bytes --]
[-- Attachment #5: rfcomm-tester.log --]
[-- Type: application/octet-stream, Size: 11684 bytes --]
[-- Attachment #6: sco-tester.log --]
[-- Type: application/octet-stream, Size: 13924 bytes --]
[-- Attachment #7: smp-tester.log --]
[-- Type: application/octet-stream, Size: 11830 bytes --]
[-- Attachment #8: userchan-tester.log --]
[-- Type: application/octet-stream, Size: 6372 bytes --]
next prev parent reply other threads:[~2021-10-22 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 17:42 [PATCH net-next 0/2] bluetooth: don't write directly to netdev->dev_addr Jakub Kicinski
2021-10-22 17:42 ` [PATCH net-next 1/2] bluetooth: use eth_hw_addr_set() Jakub Kicinski
2021-10-22 18:11 ` bluez.test.bot [this message]
2021-10-22 17:42 ` [PATCH net-next 2/2] bluetooth: use dev_addr_set() Jakub Kicinski
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=6172febe.1c69fb81.1da30.99a9@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=kuba@kernel.org \
--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 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.