From: Vinod Koul <vkoul@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, dmaengine@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/5] dma/arm64: qcom: use one compatible also for 0x10000 offset
Date: Wed, 19 Oct 2022 18:19:25 +0530 [thread overview]
Message-ID: <Y0/yVdVaZ0PNSRPN@matsya> (raw)
In-Reply-To: <20221018230352.1238479-1-krzysztof.kozlowski@linaro.org>
On 18-10-22, 19:03, Krzysztof Kozlowski wrote:
> Hi,
>
> Dependencies
> ============
> 1. DT bindings and DMA driver change depends contextually on:
> https://lore.kernel.org/all/20221018005740.23952-1-mailingradian@gmail.com/
>
> 2. DTS patches are independent, although they will spark some dtbs_check
> warnings (due to change in bindings).
Applied 1-2, thanks
--
~Vinod
next prev parent reply other threads:[~2022-10-19 13:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 23:03 [PATCH v2 0/5] dma/arm64: qcom: use one compatible also for 0x10000 offset Krzysztof Kozlowski
2022-10-18 23:03 ` [PATCH v2 1/5] dt-bindings: dma: qcom: gpi: Use sm6350 fallback Krzysztof Kozlowski
2022-10-18 23:03 ` [PATCH v2 2/5] dmaengine: qcom: gpi: Document preferred SM6350 binding Krzysztof Kozlowski
2022-10-18 23:03 ` [PATCH v2 3/5] arm64: dts: qcom: sc7280: Add GPI DMA compatible fallback Krzysztof Kozlowski
2022-10-18 23:03 ` [PATCH v2 4/5] arm64: dts: qcom: sm8350: " Krzysztof Kozlowski
2022-10-18 23:03 ` [PATCH v2 5/5] arm64: dts: qcom: sm8450: " Krzysztof Kozlowski
2022-10-19 12:49 ` Vinod Koul [this message]
2022-11-07 3:12 ` (subset) [PATCH v2 0/5] dma/arm64: qcom: use one compatible also for 0x10000 offset Bjorn Andersson
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=Y0/yVdVaZ0PNSRPN@matsya \
--to=vkoul@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.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