Linux PCI subsystem development
 help / color / mirror / Atom feed
From: "Krzysztof Wilczyński" <kw@linux.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Niklas Cassel <cassel@kernel.org>,
	Vidya Sagar <vidyas@nvidia.com>,
	lpieralisi@kernel.org, manivannan.sadhasivam@linaro.org,
	robh@kernel.org, bhelgaas@google.com, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org, treding@nvidia.com,
	jonathanh@nvidia.com, kthota@nvidia.com, mmaddireddy@nvidia.com,
	sagar.tv@gmail.com
Subject: Re: [PATCH V4] PCI: dwc: tegra194: Broaden architecture dependency
Date: Thu, 8 May 2025 22:22:36 +0900	[thread overview]
Message-ID: <20250508132236.GB2764898@rocinante> (raw)
In-Reply-To: <a6dx377rhakpl3gvvyofdbui5sbccf3fhw6o2qb55fmmx4v4fv@ifvzdjep2kp5>

Hello,

[...]
> Alternatively, since these are only platform-related Kconfig changes, I
> could pick this up into the Tegra tree if I get Acked-bys from both
> subsystems.

No objections!  Go ahead, and thank you! :)

	Krzysztof

  reply	other threads:[~2025-05-08 13:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17  7:46 [PATCH V3] PCI: dwc: tegra194: Broaden architecture dependency Vidya Sagar
2025-04-17  7:51 ` Niklas Cassel
2025-04-18 11:18   ` Vinod Koul
2025-04-18 17:21 ` Manivannan Sadhasivam
2025-05-05  6:47   ` Vidya Sagar
     [not found]   ` <SN7PR12MB8028F87148D1B635F832EEB9B88E2@SN7PR12MB8028.namprd12.prod.outlook.com>
2025-05-05  8:24     ` Manivannan Sadhasivam
2025-05-08  5:19 ` [PATCH V4] " Vidya Sagar
2025-05-08 12:17   ` Niklas Cassel
2025-05-08 12:51     ` Thierry Reding
2025-05-08 13:22       ` Krzysztof Wilczyński [this message]
2025-05-08 13:20   ` Krzysztof Wilczyński
2025-05-14 11:38   ` Vinod Koul
2025-05-14 13:02     ` Niklas Cassel
2025-05-14 13:17       ` Vinod Koul
2025-05-15 11:33         ` Manivannan Sadhasivam
2026-01-05 12:20   ` Manivannan Sadhasivam

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=20250508132236.GB2764898@rocinante \
    --to=kw@linux.com \
    --cc=bhelgaas@google.com \
    --cc=cassel@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=kthota@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=mmaddireddy@nvidia.com \
    --cc=robh@kernel.org \
    --cc=sagar.tv@gmail.com \
    --cc=thierry.reding@gmail.com \
    --cc=treding@nvidia.com \
    --cc=vidyas@nvidia.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