public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@kernel.org>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: Lorenzo Pieralisi <lpieralisi@kernel.org>,
	 Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [GIT PULL] PCI: tegra: Changes for v7.1-rc1
Date: Tue, 7 Apr 2026 10:28:39 +0200	[thread overview]
Message-ID: <adS_spOOPBkD8E1r@orome> (raw)
In-Reply-To: <lduiidifejglrep2laxzk2hep5rxpm3ysz5cwhdsglf6ciyjp4@z2dmnlvi7nhi>

[-- Attachment #1: Type: text/plain, Size: 2130 bytes --]

On Thu, Apr 02, 2026 at 10:29:34PM +0530, Manivannan Sadhasivam wrote:
> On Thu, Apr 02, 2026 at 01:56:48PM +0200, Thierry Reding wrote:
> > On Sun, Mar 29, 2026 at 05:50:39PM +0200, Thierry Reding wrote:
> > > From: Thierry Reding <thierry.reding@gmail.com>
> > > 
> > > Hi Lorenzo, Bjorn,
> > > 
> > > The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
> > > 
> > >   Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
> > > 
> > > are available in the Git repository at:
> > > 
> > >   git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.1-pci
> > > 
> > > for you to fetch changes up to a0c0906bb09ee2f64690b3b8ffb458b4dbbcb26e:
> > > 
> > >   PCI: tegra: Add Tegra264 support (2026-03-28 15:00:05 +0100)
> > > 
> > > This is v3 of the Tegra264 PCI patches that can be found here:
> > > 
> > >   https://lore.kernel.org/linux-pci/20260326135855.2795149-1-thierry.reding@kernel.org/
> > > 
> > > This looks ready now, but if there's any more feedback, I will happily
> > > respin these driver patches.
> > > 
> > > Note that the shortlog and the diffstat below include the dependencies
> > > from the Tegra tree, and that subset will go in through the ARM SoC tree
> > > as well. Effectively what's new in this pull request is just the two PCI
> > > patches, the rest is only included here to resolve the build time
> > > dependencies.
> > 
> > I'm retracting this PR. DT maintainers aren't happy about how I handled
> > this, so it'll have to wait for another release cycle.
> > 
> 
> JFYI, We don't pull from PCI patches from other trees. We only merge them by
> ourselves.

To clarify this again: the build dependencies are non-trivial and they
can't all go through the PCI tree because there are dependencies with at
least the Tegra tree, hence why a shared branch seemed the best solution
in this case.

But I guess this is all too complicated for everyone involved, so we'll
just try to get in the build dependencies for 7.1 and then defer the PCI
driver until 7.2. That way everyone can follow their standard process.

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2026-04-07  8:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-29 15:50 [GIT PULL] PCI: tegra: Changes for v7.1-rc1 Thierry Reding
2026-04-02 11:56 ` Thierry Reding
2026-04-02 16:59   ` Manivannan Sadhasivam
2026-04-07  8:28     ` Thierry Reding [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=adS_spOOPBkD8E1r@orome \
    --to=thierry.reding@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mani@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