Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Message-ID: <5f6296f0.1c69fb81.b0d4e.9db0@mx.google.com>
Date:   Wed, 16 Sep 2020 15:51:28 -0700 (PDT)
Content-Type: multipart/mixed; boundary="===============4868024934633137905=="
MIME-Version: 1.0
From:   bluez.test.bot@gmail.com
To:     linux-bluetooth@vger.kernel.org, sonnysasaka@chromium.org
Subject: RE: [BlueZ] a2dp: Keep track of ref ownership of a2dp_setup
Reply-To: linux-bluetooth@vger.kernel.org
In-Reply-To: <20200916211122.127881-1-sonnysasaka@chromium.org>
References: <20200916211122.127881-1-sonnysasaka@chromium.org>
Precedence: bulk

--===============4868024934633137905==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit


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:
checkgitlint Failed

Outputs:
28: B1 Line exceeds max length (81>80): "    frame #5: 0xf679523c libglib-2.0.so.0`g_main_context_dispatch at gmain.c:3182"
32: B1 Line exceeds max length (85>80): "    frame #9: 0x0c65a7ea bluetoothd`mainloop_run_with_signal at mainloop-notify.c:201"


---
Regards,
Linux Bluetooth

--===============4868024934633137905==--