From: Alex Elder <elder@ieee.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
davem@davemloft.net, kuba@kernel.org
Cc: Alex Elder <elder@linaro.org>,
agross@kernel.org, robh+dt@kernel.org, evgreen@chromium.org,
cpratapa@codeaurora.org, subashab@codeaurora.org,
elder@kernel.org, linux-arm-msm@vger.kernel.org,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] arm64: dts: qcom: DTS updates
Date: Mon, 26 Jul 2021 10:44:56 -0500 [thread overview]
Message-ID: <01beb264-0f25-fb50-29fc-15b6941de422@ieee.org> (raw)
In-Reply-To: <YPby3eJmDmNlESC8@yoga>
On 7/20/21 10:59 AM, Bjorn Andersson wrote:
> On Tue 20 Jul 09:20 CDT 2021, patchwork-bot+netdevbpf@kernel.org wrote:
>
>> Hello:
>>
>> This series was applied to netdev/net-next.git (refs/heads/master):
>>
>
> David, Jakub, can you please revert/drop the two "arm64: dts" patches
> from the net-next tree?
David, I intended for this series to go through the Qualcomm repository
rather than net-next, to avoid any conflicts with other updates to the
affected DTS file. The only indication I made was by having you and
Jakub in the "Cc" list rather than "To" list; in the future I will be
more obvious in the cover page.
Would you please revert the entire merge, so that these commits can
go through the Qualcomm repository? These are the commits (in order):
6a0eb6c9d9341 dt-bindings: net: qcom,ipa: make imem interconnect optional
f8bd3c82bf7d7 arm64: dts: qcom: sc7280: add IPA information
fd0f72c34bd96 arm64: dts: qcom: sc7180: define ipa_fw_mem node
b79c6fba6cd7c Merge branch 'qcom-dts-updates'
If there is another way you think this should be handled, please
explain. Thanks.
-Alex
>
> DTS patches are generally merged through the qcom and ultimately soc
> tree and I have a number of patches queued up in both sc7180 and sc7280
> that will cause merge conflicts down the road, so I would prefer to pick
> these up as well.
>
> Regards,
> Bjorn
>
>> On Mon, 19 Jul 2021 16:24:53 -0500 you wrote:
>>> This series updates some IPA-related DT nodes.
>>>
>>> Newer versions of IPA do not require an interconnect between IPA
>>> and SoC internal memory. The first patch updates the DT binding
>>> to reflect this.
>>>
>>> The second patch adds IPA information to "sc7280.dtsi", using only
>>> two interconnects. It includes the definition of the reserved
>>> memory area used to hold IPA firmware.
>>>
>>> [...]
>>
>> Here is the summary with links:
>> - [net-next,1/3] dt-bindings: net: qcom,ipa: make imem interconnect optional
>> https://git.kernel.org/netdev/net-next/c/6a0eb6c9d934
>> - [net-next,2/3] arm64: dts: qcom: sc7280: add IPA information
>> https://git.kernel.org/netdev/net-next/c/f8bd3c82bf7d
>> - [net-next,3/3] arm64: dts: qcom: sc7180: define ipa_fw_mem node
>> https://git.kernel.org/netdev/net-next/c/fd0f72c34bd9
>>
>> You are awesome, thank you!
>> --
>> Deet-doot-dot, I am a bot.
>> https://korg.docs.kernel.org/patchwork/pwbot.html
>>
>>
prev parent reply other threads:[~2021-07-26 15:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 21:24 [PATCH net-next 0/3] arm64: dts: qcom: DTS updates Alex Elder
2021-07-19 21:24 ` [PATCH net-next 1/3] dt-bindings: net: qcom,ipa: make imem interconnect optional Alex Elder
2021-07-23 20:52 ` Rob Herring
2021-07-26 15:59 ` Alex Elder
2021-07-28 15:33 ` Rob Herring
2021-08-03 12:24 ` Alex Elder
2021-08-03 18:05 ` Rob Herring
2021-07-19 21:24 ` [PATCH net-next 2/3] arm64: dts: qcom: sc7280: add IPA information Alex Elder
2021-07-19 21:24 ` [PATCH net-next 3/3] arm64: dts: qcom: sc7180: define ipa_fw_mem node Alex Elder
2021-07-20 14:20 ` [PATCH net-next 0/3] arm64: dts: qcom: DTS updates patchwork-bot+netdevbpf
2021-07-20 15:59 ` Bjorn Andersson
2021-07-26 15:44 ` Alex Elder [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=01beb264-0f25-fb50-29fc-15b6941de422@ieee.org \
--to=elder@ieee.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=cpratapa@codeaurora.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=elder@kernel.org \
--cc=elder@linaro.org \
--cc=evgreen@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=subashab@codeaurora.org \
/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).