All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Jim Quinlan <james.quinlan@broadcom.com>
Cc: "Jim Quinlan" <jim2101024@gmail.com>,
	linux-pci <linux-pci@vger.kernel.org>,
	"Nicolas Saenz Julienne" <nsaenz@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"James Dutton" <james.dutton@gmail.com>,
	"Cyril Brulebois" <kibi@debian.org>,
	bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
	"Florian Fainelli" <f.fainelli@gmail.com>,
	"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
	<linux-rpi-kernel@lists.infradead.org>,
	"moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>,
	"open list" <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH v1] PCI: brcmstb: Fix regression regarding missing PCIe linkup
Date: Fri, 27 May 2022 20:59:21 -0500	[thread overview]
Message-ID: <20220528015921.GA524446@bhelgaas> (raw)
In-Reply-To: <CA+-6iNzfT1Ut3P-mn3kL=ZUdso+FV9KJUpQzOZpQfpJAT7BTkQ@mail.gmail.com>

On Fri, May 27, 2022 at 08:19:16PM -0400, Jim Quinlan wrote:
> On Fri, May 27, 2022 at 7:28 PM Bjorn Helgaas <helgaas@kernel.org> wrote:

> > Where are we at with this?  Linus just merged my pull request, and I'd
> > really like to get this resolved before -rc1 (expected June 5 or so),
> > which means I'd like to ask him to pull the fix early next week.
>
> I was waiting to see where the email thread was going...

My fault for raising all the tangents :)

> I'll send out the v2 regression fix in less than 24 hours.

Great, thanks!

WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Helgaas <helgaas@kernel.org>
To: Jim Quinlan <james.quinlan@broadcom.com>
Cc: "Jim Quinlan" <jim2101024@gmail.com>,
	linux-pci <linux-pci@vger.kernel.org>,
	"Nicolas Saenz Julienne" <nsaenz@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"James Dutton" <james.dutton@gmail.com>,
	"Cyril Brulebois" <kibi@debian.org>,
	bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
	"Florian Fainelli" <f.fainelli@gmail.com>,
	"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
	<linux-rpi-kernel@lists.infradead.org>,
	"moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>,
	"open list" <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH v1] PCI: brcmstb: Fix regression regarding missing PCIe linkup
Date: Fri, 27 May 2022 20:59:21 -0500	[thread overview]
Message-ID: <20220528015921.GA524446@bhelgaas> (raw)
In-Reply-To: <CA+-6iNzfT1Ut3P-mn3kL=ZUdso+FV9KJUpQzOZpQfpJAT7BTkQ@mail.gmail.com>

On Fri, May 27, 2022 at 08:19:16PM -0400, Jim Quinlan wrote:
> On Fri, May 27, 2022 at 7:28 PM Bjorn Helgaas <helgaas@kernel.org> wrote:

> > Where are we at with this?  Linus just merged my pull request, and I'd
> > really like to get this resolved before -rc1 (expected June 5 or so),
> > which means I'd like to ask him to pull the fix early next week.
>
> I was waiting to see where the email thread was going...

My fault for raising all the tangents :)

> I'll send out the v2 regression fix in less than 24 hours.

Great, thanks!

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-05-28  1:59 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18 19:42 [PATCH v1] PCI: brcmstb: Fix regression regarding missing PCIe linkup Jim Quinlan
2022-05-18 19:42 ` Jim Quinlan
2022-05-18 22:18 ` Bjorn Helgaas
2022-05-18 22:18   ` Bjorn Helgaas
2022-05-19  6:47   ` Cyril Brulebois
2022-05-19  6:47     ` Cyril Brulebois
2022-05-19 16:10 ` Bjorn Helgaas
2022-05-19 16:10   ` Bjorn Helgaas
2022-05-19 18:04   ` Jim Quinlan
2022-05-19 18:04     ` Jim Quinlan
2022-05-19 19:58     ` Jim Quinlan
2022-05-19 19:58       ` Jim Quinlan
2022-05-21 16:43 ` Bjorn Helgaas
2022-05-21 16:43   ` Bjorn Helgaas
2022-05-21 18:51   ` Jim Quinlan
2022-05-21 18:51     ` Jim Quinlan
2022-05-23 22:10     ` Bjorn Helgaas
2022-05-23 22:10       ` Bjorn Helgaas
2022-05-24 16:54       ` Jim Quinlan
2022-05-24 16:54         ` Jim Quinlan
2022-05-24 23:56         ` Cyril Brulebois
2022-05-24 23:56           ` Cyril Brulebois
2022-05-25 17:13           ` Jim Quinlan
2022-05-25 17:13             ` Jim Quinlan
2022-05-25  7:21         ` Stefan Wahren
2022-05-25  7:21           ` Stefan Wahren
2022-05-25 17:24           ` Jim Quinlan
2022-05-25 17:24             ` Jim Quinlan
2022-05-25 21:57         ` Bjorn Helgaas
2022-05-25 21:57           ` Bjorn Helgaas
2022-05-27  6:50           ` Francesco Dolcini
2022-05-27  6:50             ` Francesco Dolcini
2022-05-27 23:27           ` Bjorn Helgaas
2022-05-27 23:27             ` Bjorn Helgaas
2022-05-28  0:19             ` Jim Quinlan
2022-05-28  0:19               ` Jim Quinlan
2022-05-28  1:59               ` Bjorn Helgaas [this message]
2022-05-28  1:59                 ` Bjorn Helgaas
2022-05-26 19:25       ` Rob Herring
2022-05-26 19:25         ` Rob Herring
2022-05-26 20:53         ` Bjorn Helgaas
2022-05-26 20:53           ` Bjorn Helgaas
2022-05-31 19:46           ` Rob Herring
2022-05-31 19:46             ` Rob Herring

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=20220528015921.GA524446@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=bhelgaas@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=james.dutton@gmail.com \
    --cc=james.quinlan@broadcom.com \
    --cc=jim2101024@gmail.com \
    --cc=kibi@debian.org \
    --cc=kw@linux.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=nsaenz@kernel.org \
    --cc=rjw@rjwysocki.net \
    --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 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.