linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, d.grigorev@omprussia.ru
Subject: RE: [BlueZ,v2] gobex: Fix segfault caused by interrupted transfer
Date: Fri, 05 Jun 2020 04:36:03 -0700 (PDT)	[thread overview]
Message-ID: <5eda2e23.1c69fb81.a0d93.2161@mx.google.com> (raw)
In-Reply-To: <20200605111859.7742-1-d.grigorev@omprussia.ru>

[-- Attachment #1: Type: text/plain, Size: 2386 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.
While we are preparing for reviewing the patches, we found the following
issue/warning.

Test Result:
checkpatch Failed

Outputs:
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#14: 
0xecc6eeda in dbus_connection_get_object_path_data () from /usr/lib/libdbus-1.so.3

WARNING:UNKNOWN_COMMIT_ID: Unknown commit id '2baea85dec1a', maybe rebased or not pulled?
#32: 
commit 2baea85dec1a ("Bluetooth: L2CAP ERTM shutdown protect sk and chan")

WARNING:UNKNOWN_COMMIT_ID: Unknown commit id 'f65468f6e26c', maybe rebased or not pulled?
#33: 
commit f65468f6e26c ("Bluetooth: Make __l2cap_wait_ack more efficient")

WARNING:UNKNOWN_COMMIT_ID: Unknown commit id '451e4c6c6b3f', maybe rebased or not pulled?
#34: 
commit 451e4c6c6b3f ("Bluetooth: Add BT_DBG to l2cap_sock_shutdown()")

WARNING:UNKNOWN_COMMIT_ID: Unknown commit id 'cb02a25583b5', maybe rebased or not pulled?
#35: 
commit cb02a25583b5 ("Bluetooth: __l2cap_wait_ack() use msecs_to_jiffies()")

WARNING:UNKNOWN_COMMIT_ID: Unknown commit id 'e432c72c464d', maybe rebased or not pulled?
#36: 
commit e432c72c464d ("Bluetooth: __l2cap_wait_ack() add defensive timeout")

WARNING:UNKNOWN_COMMIT_ID: Unknown commit id 'e7456437c15a', maybe rebased or not pulled?
#37: 
commit e7456437c15a ("Bluetooth: Unwind l2cap_sock_shutdown()")

WARNING:UNKNOWN_COMMIT_ID: Unknown commit id '04ba72e6b24f', maybe rebased or not pulled?
#38: 
commit 04ba72e6b24f ("Bluetooth: Reorganize mutex lock in l2cap_sock_shutdown()")

WARNING:UNKNOWN_COMMIT_ID: Unknown commit id '9f7378a9d6ce', maybe rebased or not pulled?
#39: 
commit 9f7378a9d6ce ("Bluetooth: l2cap_disconnection_req priority over shutdown")

- total: 0 errors, 9 warnings, 34 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.

Your patch has style problems, please review.

NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPLIT_STRING

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.



---
Regards,
Linux Bluetooth

  reply	other threads:[~2020-06-05 11:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-05 11:18 [PATCH BlueZ v2] gobex: Fix segfault caused by interrupted transfer Denis Grigorev
2020-06-05 11:36 ` bluez.test.bot [this message]
2020-06-05 11:36 ` [BlueZ,v2] " 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=5eda2e23.1c69fb81.a0d93.2161@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=d.grigorev@omprussia.ru \
    --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;
as well as URLs for NNTP newsgroup(s).