[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8d6af7e2-76f8-4daa-a751-a1abe29af103@kernel.org>
Date: Thu, 20 Jun 2024 16:35:16 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: patchwork-bot+bluetooth@...nel.org, Bartosz Golaszewski <brgl@...ev.pl>,
luiz.dentz@...il.com
Cc: marcel@...tmann.org, krzk+dt@...nel.org, linux-bluetooth@...r.kernel.org,
netdev@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, bartosz.golaszewski@...aro.org
Subject: Re: [GIT PULL] Immutable tag between the Bluetooth and pwrseq
branches for v6.11-rc1
On 20/06/2024 16:30, patchwork-bot+bluetooth@...nel.org wrote:
> Hello:
>
> This pull request was applied to bluetooth/bluetooth-next.git (master)
> by Luiz Augusto von Dentz <luiz.von.dentz@...el.com>:
>
> On Wed, 12 Jun 2024 09:58:29 +0200 you wrote:
>> From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
>>
>> Hi Marcel, Luiz,
>>
>> Please pull the following power sequencing changes into the Bluetooth tree
>> before applying the hci_qca patches I sent separately.
>>
>> [...]
>
> Here is the summary with links:
> - [GIT,PULL] Immutable tag between the Bluetooth and pwrseq branches for v6.11-rc1
> https://git.kernel.org/bluetooth/bluetooth-next/c/4c318a2187f8
Luiz,
This pulls looks wrong. Are you sure you have correct base? The diffstat
suggests you are merging into rc2, not rc3. This will be confusing in
merge commit. It is much safer, including possible feedback from Linus,
if you use exactly the same base.
Best regards,
Krzysztof
Powered by blists - more mailing lists