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]
Message-ID: <0b144517-4cc5-4c23-be57-d6f5323690ec@163.com>
Date: Fri, 21 Jun 2024 09:14:30 +0800
From: Lk Sii <lk_sii@....com>
To: patchwork-bot+bluetooth@...nel.org, Bartosz Golaszewski <brgl@...ev.pl>
Cc: marcel@...tmann.org, luiz.dentz@...il.com, davem@...emloft.net,
 edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com, robh@...nel.org,
 krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org, kvalo@...nel.org,
 andersson@...nel.org, konrad.dybcio@...aro.org, lgirdwood@...il.com,
 broonie@...nel.org, catalin.marinas@....com, will@...nel.org,
 bhelgaas@...gle.com, saravanak@...gle.com, geert+renesas@...der.be,
 arnd@...db.de, neil.armstrong@...aro.org, m.szyprowski@...sung.com,
 elder@...aro.org, srinivas.kandagatla@...aro.org,
 gregkh@...uxfoundation.org, abel.vesa@...aro.org, mani@...nel.org,
 lukas@...ner.de, dmitry.baryshkov@...aro.org, amit.pundir@...aro.org,
 wuxilin123@...il.com, linux-bluetooth@...r.kernel.org,
 netdev@...r.kernel.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org,
 linux-arm-msm@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
 linux-pci@...r.kernel.org, linux-pm@...r.kernel.org,
 bartosz.golaszewski@...aro.org
Subject: Re: [PATCH v9 0/2] pwrseq: introduce the subsystem and first driver



On 2024/6/20 22:30, patchwork-bot+bluetooth@...nel.org wrote:
> Hello:
> 
> This series was applied to bluetooth/bluetooth-next.git (master)
> by Bartosz Golaszewski <bartosz.golaszewski@...aro.org>:
> 
Hi luiz,

i am curious why Bartosz is able to merge his changes into bluetooth
development tree bluetooth-next directly.

1)
his changes should belong to *POWER* scope instead of *Bluetooth*
obviously, however, there are *NOT* any SOB tag from either power and
bluetooth maintainer. these changes currently only have below Acked-by
and Signed-off-by tags:

Acked-by: Krzysztof Kozlowski <krzk@...nel.org>
Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>

2)
his changes have not merged into linus mainline tree yet.

3)
perhaps, it is safer to pull his changes from linus mainline tree when
merged than to merge into bluetooth-next firstly.

> On Wed,  5 Jun 2024 14:38:48 +0200 you wrote:
>> From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
>>
>> Hi!
>>
>> These are the power sequencing patches sent separately after some
>> improvements suggested by Bjorn Helgaas. I intend to pick them up into a
>> new branch and maintain the subsystem from now on. I then plan to
>> provide an immutable tag to the Bluetooth and PCI subsystems so that the
>> rest of the C changes can be applied. This new branch will then be
>> directly sent to Linus Torvalds for the next merge window.
>>
>> [...]
> 
> Here is the summary with links:
>   - [v9,1/2] power: sequencing: implement the pwrseq core
>     https://git.kernel.org/bluetooth/bluetooth-next/c/249ebf3f65f8
>   - [v9,2/2] power: pwrseq: add a driver for the PMU module on the QCom WCN chipsets
>     https://git.kernel.org/bluetooth/bluetooth-next/c/2f1630f437df
> 
> You are awesome, thank you!


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ