Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-1670-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Precedence: bulk
MIME-Version: 1.0
References: <20240207040110.398884-1-user@LBTOE> <65c3655f.170a0220.e7119.2a26@mx.google.com>
In-Reply-To: <65c3655f.170a0220.e7119.2a26@mx.google.com>
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Date: Wed, 7 Feb 2024 11:10:48 -0500
Message-ID: <CABBYNZLJZPH1gag5YBcdxjL=YY0o3ySnLA5DvUBqt0xVPcqfAA@mail.gmail.com>
Subject: Re: [BlueZ] monitor/att: Enable the notification logging support for
 the CCP
To: linux-bluetooth@vger.kernel.org
Cc: shahid.bashir.vichhi.com@web.codeaurora.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Shahid,

On Wed, Feb 7, 2024 at 6:11=E2=80=AFAM <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: monitor/att.c:3481
> error: monitor/att.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.

You probably need to rebase these changes on top of master with
something like git pull --rebase origin/master, if you had cloned it
from github then you probably need to either add a new remote or do a
new clone, anyway Id recommend always have the origin remote pointing
to the main tree not the github mirror.

--=20
Luiz Augusto von Dentz