All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-arm-msm@kernel.org
To: Alex Elder <elder@linaro.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 0/3] arm64: dts: fixes
Date: Thu, 26 Nov 2020 19:50:06 +0000	[thread overview]
Message-ID: <160642020611.4652.12882405129721397036.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201126015457.6557-1-elder@linaro.org>

Hello:

This series was applied to qcom/linux.git (refs/heads/for-next):

On Wed, 25 Nov 2020 19:54:54 -0600 you wrote:
> The first patch in this series changes the IOMMU specification for
> the IPA node in "sc7180.dtsi" to identify two streams distinctly,
> rather than specifying them with a mask.  This was inspired by
> something Bjorn did recently for IPA in "sdm845.dtsi".
> 
> The second and third just replace 0 with GIC_SPI in two IPA
> interrupt specifications.
> 
> [...]

Here is the summary with links:
  - [1/3] arm64: dts: qcom: sc7180: limit IPA iommu streams
    https://git.kernel.org/qcom/c/8f34831d3659
  - [2/3] arm64: dts: qcom: sc7180: use GIC_SPI for IPA interrupts
    https://git.kernel.org/qcom/c/cfee3ea05cf2
  - [3/3] arm64: dts: qcom: sdm845: use GIC_SPI for IPA interrupts
    https://git.kernel.org/qcom/c/0fc0f4b6aded

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2020-11-26 19:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26  1:54 [PATCH 0/3] arm64: dts: fixes Alex Elder
2020-11-26  1:54 ` [PATCH 1/3] arm64: dts: qcom: sc7180: limit IPA iommu streams Alex Elder
2020-11-26 17:47   ` Bjorn Andersson
2020-11-26  1:54 ` [PATCH 2/3] arm64: dts: qcom: sc7180: use GIC_SPI for IPA interrupts Alex Elder
2020-11-26  1:54 ` [PATCH 3/3] arm64: dts: qcom: sdm845: " Alex Elder
2020-11-26 19:50 ` patchwork-bot+linux-arm-msm [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=160642020611.4652.12882405129721397036.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-arm-msm@kernel.org \
    --cc=elder@linaro.org \
    --cc=linux-arm-msm@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.