Devicetree
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: lpieralisi@kernel.org, kw@linux.com, robh@kernel.org,
	bhelgaas@google.com, konradybcio@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: (subset) [PATCH 0/2] PCI: qcom-ep: BAR fixes
Date: Tue,  7 Jan 2025 22:43:42 -0600	[thread overview]
Message-ID: <173631142072.110881.6854526601749603529.b4-ty@kernel.org> (raw)
In-Reply-To: <20241231130224.38206-1-manivannan.sadhasivam@linaro.org>


On Tue, 31 Dec 2024 18:32:22 +0530, Manivannan Sadhasivam wrote:
> This series has a couple of fixes for Qcom PCIe endpoint controller. The dts
> patch fixes the size of the 'addr_space' regions that allows the endpoint
> drivers to request and map BARs of size >= 1MB. The driver patch marks BAR0/BAR2
> as 64bit BARs.
> 
> Previously, this series was part of the Kselftest series [1]. But submitting
> separately as these are independent fixes anyway.
> 
> [...]

Applied, thanks!

[1/2] arm64: dts: qcom: sa8775p: Fix the size of 'addr_space' regions
      commit: ec2f548e1a92f49f765e2bce14ceed34698514fc

Best regards,
-- 
Bjorn Andersson <andersson@kernel.org>

      parent reply	other threads:[~2025-01-08  4:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-31 13:02 [PATCH 0/2] PCI: qcom-ep: BAR fixes Manivannan Sadhasivam
2024-12-31 13:02 ` [PATCH 1/2] arm64: dts: qcom: sa8775p: Fix the size of 'addr_space' regions Manivannan Sadhasivam
2024-12-31 13:02 ` [PATCH 2/2] PCI: qcom-ep: Mark BAR0/BAR2 as 64bit BARs and BAR1/BAR3 as RESERVED Manivannan Sadhasivam
2025-02-20 15:33   ` Krzysztof Wilczyński
2025-01-08  4:43 ` Bjorn Andersson [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=173631142072.110881.6854526601749603529.b4-ty@kernel.org \
    --to=andersson@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=kw@linux.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=robh@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