linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, matthias.schiffer@ew.tq-group.com
Subject: RE: [BlueZ,1/2] tools/rfcomm: reset ignored signals after fork
Date: Thu, 15 Feb 2024 02:22:37 -0800 (PST)	[thread overview]
Message-ID: <65cde5ed.e90a0220.f6974.106a@mx.google.com> (raw)
In-Reply-To: <20240215083954.5233-1-matthias.schiffer@ew.tq-group.com>

[-- Attachment #1: Type: text/plain, Size: 2111 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=826253

---Test result---

Test Summary:
CheckPatch                    PASS      0.92 seconds
GitLint                       PASS      0.65 seconds
BuildEll                      PASS      24.66 seconds
BluezMake                     PASS      734.12 seconds
MakeCheck                     PASS      12.14 seconds
MakeDistcheck                 PASS      167.46 seconds
CheckValgrind                 PASS      230.99 seconds
CheckSmatch                   PASS      334.58 seconds
bluezmakeextell               PASS      109.28 seconds
IncrementalBuild              PASS      1378.20 seconds
ScanBuild                     WARNING   985.95 seconds

Details
##############################
Test: ScanBuild - WARNING
Desc: Run Scan Build
Output:
tools/rfcomm.c:234:3: warning: Value stored to 'i' is never read
                i = execvp(cmdargv[0], cmdargv);
                ^   ~~~~~~~~~~~~~~~~~~~~~~~~~~~
tools/rfcomm.c:234:7: warning: Null pointer passed to 1st parameter expecting 'nonnull'
                i = execvp(cmdargv[0], cmdargv);
                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~
tools/rfcomm.c:354:8: warning: Although the value stored to 'fd' is used in the enclosing expression, the value is never actually read from 'fd'
                if ((fd = open(devname, O_RDONLY | O_NOCTTY)) < 0) {
                     ^    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
tools/rfcomm.c:497:14: warning: Assigned value is garbage or undefined
        req.channel = raddr.rc_channel;
                    ^ ~~~~~~~~~~~~~~~~
tools/rfcomm.c:515:8: warning: Although the value stored to 'fd' is used in the enclosing expression, the value is never actually read from 'fd'
                if ((fd = open(devname, O_RDONLY | O_NOCTTY)) < 0) {
                     ^    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
5 warnings generated.



---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2024-02-15 10:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-15  8:39 [PATCH BlueZ 1/2] tools/rfcomm: reset ignored signals after fork Matthias Schiffer
2024-02-15  8:39 ` [PATCH BlueZ 2/2] tools/rfcomm: _exit() on execvp() failure Matthias Schiffer
2024-02-15 10:22 ` bluez.test.bot [this message]
2024-02-20 13:50 ` [PATCH BlueZ 1/2] tools/rfcomm: reset ignored signals after fork patchwork-bot+bluetooth

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=65cde5ed.e90a0220.f6974.106a@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=matthias.schiffer@ew.tq-group.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).