lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 20 Jun 2024 10:44:33 -0400
From: Luiz Augusto von Dentz <luiz.dentz@...il.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: patchwork-bot+bluetooth@...nel.org, Bartosz Golaszewski <brgl@...ev.pl>, 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

Hi Krzysztof,

On Thu, Jun 20, 2024 at 10:35 AM Krzysztof Kozlowski <krzk@...nel.org> wrote:
>
> 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.

So you are saying I need to rebase? I usually only rebase when it
comes the time to do a pull-request using net-next as a base since
that is where bluetooth-next normally lands.

> Best regards,
> Krzysztof
>


-- 
Luiz Augusto von Dentz

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ