devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Lk Sii <lk_sii@163.com>,
	patchwork-bot+bluetooth@kernel.org,
	Bartosz Golaszewski <brgl@bgdev.pl>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	robh@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	conor+dt@kernel.org, kvalo@kernel.org, andersson@kernel.org,
	konrad.dybcio@linaro.org, lgirdwood@gmail.com,
	broonie@kernel.org, catalin.marinas@arm.com, will@kernel.org,
	bhelgaas@google.com, saravanak@google.com,
	geert+renesas@glider.be, arnd@arndb.de,
	neil.armstrong@linaro.org, m.szyprowski@samsung.com,
	elder@linaro.org, srinivas.kandagatla@linaro.org,
	gregkh@linuxfoundation.org, abel.vesa@linaro.org,
	mani@kernel.org, lukas@wunner.de, dmitry.baryshkov@linaro.org,
	amit.pundir@linaro.org, wuxilin123@gmail.com,
	linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-wireless@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org,
	linux-pm@vger.kernel.org, bartosz.golaszewski@linaro.org
Subject: Re: [PATCH v9 0/2] pwrseq: introduce the subsystem and first driver
Date: Fri, 21 Jun 2024 16:50:06 +0200	[thread overview]
Message-ID: <5952f4ef-8615-4aa5-9ff6-3bee63750712@kernel.org> (raw)
In-Reply-To: <0b144517-4cc5-4c23-be57-d6f5323690ec@163.com>

On 21/06/2024 03:14, Lk Sii wrote:
> 
> 
> On 2024/6/20 22:30, patchwork-bot+bluetooth@kernel.org wrote:
>> Hello:
>>
>> This series was applied to bluetooth/bluetooth-next.git (master)
>> by Bartosz Golaszewski <bartosz.golaszewski@linaro.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:

You are trolling us or what?

That's a cross tree pull request.

> 
> Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> 
> 2)
> his changes have not merged into linus mainline tree yet.

Do you understand the concept of merge windows?

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

You are joking, right?


Best regards,
Krzysztof


      parent reply	other threads:[~2024-06-21 14:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05 12:38 [PATCH v9 0/2] pwrseq: introduce the subsystem and first driver Bartosz Golaszewski
2024-06-05 12:38 ` [PATCH v9 1/2] power: sequencing: implement the pwrseq core Bartosz Golaszewski
2024-06-10 14:50   ` Krzysztof Kozlowski
2024-06-05 12:38 ` [PATCH v9 2/2] power: pwrseq: add a driver for the PMU module on the QCom WCN chipsets Bartosz Golaszewski
2024-06-10 14:54   ` Krzysztof Kozlowski
2024-06-10 14:55     ` Bartosz Golaszewski
2024-06-10 15:00       ` Krzysztof Kozlowski
2024-06-10 15:05   ` Krzysztof Kozlowski
2024-06-10 15:07     ` Krzysztof Kozlowski
2024-06-10 14:07 ` [PATCH v9 0/2] pwrseq: introduce the subsystem and first driver Bartosz Golaszewski
2024-06-12  7:24 ` Bartosz Golaszewski
2024-06-20 14:30 ` patchwork-bot+bluetooth
2024-06-21  1:14   ` Lk Sii
2024-06-21  6:36     ` Bartosz Golaszewski
2024-06-21  9:04       ` Lk Sii
2024-06-21 13:23         ` Bartosz Golaszewski
2024-06-21 14:51         ` Krzysztof Kozlowski
2024-06-24 15:30         ` Luiz Augusto von Dentz
2024-06-21 14:50     ` Krzysztof Kozlowski [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5952f4ef-8615-4aa5-9ff6-3bee63750712@kernel.org \
    --to=krzk@kernel.org \
    --cc=abel.vesa@linaro.org \
    --cc=amit.pundir@linaro.org \
    --cc=andersson@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=bhelgaas@google.com \
    --cc=brgl@bgdev.pl \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=edumazet@google.com \
    --cc=elder@linaro.org \
    --cc=geert+renesas@glider.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kuba@kernel.org \
    --cc=kvalo@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lk_sii@163.com \
    --cc=luiz.dentz@gmail.com \
    --cc=lukas@wunner.de \
    --cc=m.szyprowski@samsung.com \
    --cc=mani@kernel.org \
    --cc=marcel@holtmann.org \
    --cc=neil.armstrong@linaro.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=patchwork-bot+bluetooth@kernel.org \
    --cc=robh@kernel.org \
    --cc=saravanak@google.com \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=will@kernel.org \
    --cc=wuxilin123@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).