linux-kernel - Re: [PATCH v9 0/2] pwrseq: introduce the subsystem and first driver

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] [day] [month] [year] [list]

Message-ID: <CABBYNZ+X+_RfZ-fVGrBHhAdbneU+613nx1NTw7+e8ep4JtF6nQ@mail.gmail.com>
Date: Mon, 24 Jun 2024 11:30:53 -0400
From: Luiz Augusto von Dentz <luiz.dentz@...il.com>
To: Lk Sii <lk_sii@....com>
Cc: Bartosz Golaszewski <brgl@...ev.pl>, patchwork-bot+bluetooth@...nel.org, marcel@...tmann.org, 
	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

Hi,

On Fri, Jun 21, 2024 at 5:05 AM Lk Sii <lk_sii@....com> wrote:
>
> On 2024/6/21 14:36, Bartosz Golaszewski wrote:
> > On Fri, Jun 21, 2024 at 3:14 AM Lk Sii <lk_sii@....com> wrote:
> >>
> >>
> >>
> >> 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.
> >>
> >
> > This conversation is getting progressively worse...
> >
> >> 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>
> >>
> >
> > It's a new subsystem that has been discussed and reviewed for months
> > and thoroughly tested. Please refer to the cover letter under v8
> > linked in this thread. It's not related to power-management or
> > power-supply, it's its own thing but IMO the best place to put it is
> > under drivers/power/. And I will maintain it.
> >
> >> 2)
> >> his changes have not merged into linus mainline tree yet.
> >>
> >
> > This is why they are in next! They are scheduled to go in during the
> > upcoming merge window. But since changes belong in multiple trees, we
> > need a cross-tree merge.
> >
> >> 3)
> >> perhaps, it is safer to pull his changes from linus mainline tree when
> >> merged than to merge into bluetooth-next firstly.
> >>
> >
> > It's not safer at all, why would spending less time in next be safer?
> >
> it seems this patch serial(new subsystem) does not depend on bluetooth
> and also does not belong to bluetooth subsystem, but have been contained
> by tip of bluetooth tree.
>
> why not follow below merging produce?
> 1) you send this patch serials to Linus to merge within linus mainline tree
> 2) luiz then pull your changes from linus mainline tree.

This was discussed already, but in case you didn't follow if we need
to incorporate changes earlier we can't really wait the merge window
for the changes to be merged first into the Linus tree. Anyway Bartosz
is the maintainer of Power Sequence subsystem, and several others
drivers, so I think it is safe to trust his judgment here.