Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20230601023835.1117866-1-yinghsu@chromium.org> <64780a7d.d40a0220.ea23f.cabd@mx.google.com>
In-Reply-To: <64780a7d.d40a0220.ea23f.cabd@mx.google.com>
From:   Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Date:   Wed, 31 May 2023 20:57:41 -0700
Message-ID: <CABBYNZ+wmNX0seeh+XeCbnL7=DozCULoRg7s+_WnM3XCnmQoTg@mail.gmail.com>
Subject: Re: [v6] Bluetooth: Fix l2cap_disconnect_req deadlock
To:     linux-bluetooth@vger.kernel.org
Cc:     yinghsu@chromium.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

Hi Ying,

On Wed, May 31, 2023 at 8:08=E2=80=AFPM <bluez.test.bot@gmail.com> wrote:
>
> This is an 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 preparing the CI tests, the patches you submitted couldn't be appli=
ed to the current HEAD of the repository.
>
> ----- Output -----
>
> error: patch failed: net/bluetooth/l2cap_core.c:4634
> error: net/bluetooth/l2cap_core.c: patch does not apply
> hint: Use 'git am --show-current-patch' to see the failed patch
>
> Please resolve the issue and submit the patches again.
>
>
> ---
> Regards,
> Linux Bluetooth

It has been pushed already:

https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.gi=
t/commit/?id=3D0e31289b2827062975194a68c0ae4d854cd87a81


--=20
Luiz Augusto von Dentz