linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: "Pali Rohár" <pali@kernel.org>
Cc: "Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	linux-pci@vger.kernel.org, "Jan Palus" <jpalus@fastmail.com>,
	"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
	"Marek Behún" <kabel@kernel.org>
Subject: Re: [Bug 215540] New: mvebu: no pcie devices detected on turris omnia (5.16.3 regression)
Date: Fri, 11 Feb 2022 13:57:44 -0600	[thread overview]
Message-ID: <20220211195744.GA728212@bhelgaas> (raw)
In-Reply-To: <20220211194330.siiwntko6b3lldw4@pali>

On Fri, Feb 11, 2022 at 08:43:30PM +0100, Pali Rohár wrote:
> On Thursday 03 February 2022 09:47:28 Bjorn Helgaas wrote:
> > [+cc Lorenzo, beginning of thread:
> > https://lore.kernel.org/r/20220127234917.GA150851@bhelgaas]
> > On Thu, Feb 03, 2022 at 01:55:28PM +0100, Pali Rohár wrote:

> > > Bjorn & Greg: How do you want to handle this situation? Should I prepare
> > > special patch for stable which fix it? Or something else?
> > > 
> > > Anyway, do you know how it could happen that patch was incorrectly
> > > auto-backported into stable? Differences between original and
> > > wrongly-modified patch looks very similar (both "bus" and "dev" keywords
> > > have same number of characters) and it was hard for me to see that there
> > > are differences. So probably overlooking could happen or maybe git or
> > > patch tools could do such small changes when doing backports?
> > 
> > Your patch on the mailing list [1] contains:
> > 
> >         mvebu_pcie_setup_hw(port);
> >         mvebu_pcie_set_local_dev_nr(port, 1);
> >   +     mvebu_pcie_set_local_bus_nr(port, 0);
> > 
> > 91a8d79fc797 ("PCI: mvebu: Fix configuring secondary bus of PCIe Root
> > Port via emulated bridge") [2] appeared in v5.17-rc1 and contains:
> > 
> >         mvebu_pcie_setup_hw(port);
> >   -     mvebu_pcie_set_local_dev_nr(port, 1);
> >   +     mvebu_pcie_set_local_dev_nr(port, 0);
> > 
> > And this is the current state of mainline [3].
> > 
> > 91a8d79fc797 was backported to v5.16.3 as 7cde9bf07316 [4], which also
> > contains:
> > 
> >         mvebu_pcie_setup_hw(port);
> >   -     mvebu_pcie_set_local_dev_nr(port, 1);
> >   +     mvebu_pcie_set_local_dev_nr(port, 0);
> > 
> > So I think the problem was a merge error when we first applied this
> > for mainline, and we just need to make a patch for mainline, apply it
> > for v5.17, and mark it for stable.
> 
> Should I prepare and send fixup patch?

Yes, please.  Sorry for the inconvenience!

> > [1] https://lore.kernel.org/r/20211125124605.25915-12-pali@kernel.org
> > [2] https://git.kernel.org/linus/91a8d79fc797
> > [3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/pci/controller/pci-mvebu.c?id=v5.17-rc2#n1323
> > [4] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.16.y&id=7cde9bf07316

  reply	other threads:[~2022-02-11 19:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-215540-41252@https.bugzilla.kernel.org/>
2022-01-27 23:49 ` [Bug 215540] New: mvebu: no pcie devices detected on turris omnia (5.16.3 regression) Bjorn Helgaas
2022-01-28  5:08   ` Thorsten Leemhuis
2022-02-03 12:26   ` Pali Rohár
2022-02-03 12:54     ` Jan Palus
2022-02-03 12:55     ` Pali Rohár
2022-02-03 13:15       ` Jan Palus
2022-02-03 15:47       ` Bjorn Helgaas
2022-02-11 19:43         ` Pali Rohár
2022-02-11 19:57           ` Bjorn Helgaas [this message]
2022-02-14 12:54             ` Pali Rohár

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=20220211195744.GA728212@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jpalus@fastmail.com \
    --cc=kabel@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=pali@kernel.org \
    --cc=thomas.petazzoni@bootlin.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;
as well as URLs for NNTP newsgroup(s).