On 21/06/2024 11:04, Lk Sii wrote: > On 2024/6/21 14:36, Bartosz Golaszewski wrote: >> On Fri, Jun 21, 2024 at 3:14 AM Lk Sii <lk_sii@xxxxxxx> wrote: >>> >>> >>> >>> On 2024/6/20 22:30, patchwork-bot+bluetooth@xxxxxxxxxx wrote: >>>> Hello: >>>> >>>> This series was applied to bluetooth/bluetooth-next.git (master) >>>> by Bartosz Golaszewski <bartosz.golaszewski@xxxxxxxxxx>: >>>> >>> 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@xxxxxxxxxx> >>> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@xxxxxxxxxx> >>> >> >> 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 is not how Linux kernel development works. Read process documents before interfering with people's work. Best regards, Krzysztof
