All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Cyril Brulebois <kibi@debian.org>,
	Florian Fainelli <f.fainelli@gmail.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
	Jim Quinlan <jim2101024@gmail.com>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Nicolas Saenz Julienne <nsaenz@kernel.org>,
	bcm-kernel-feedback-list@broadcom.com, linux-pci@vger.kernel.org,
	regressions@lists.linux.dev, Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH 0/4] PCI: brcmstb: Revert subdevice regulator stuff
Date: Wed, 11 May 2022 13:54:16 -0700	[thread overview]
Message-ID: <aaa4b4d5-486d-869c-10b7-f88c87c450fd@gmail.com> (raw)
In-Reply-To: <20220511203946.nr2qqzjlintrgxmi@mraw.org>

On 5/11/22 13:39, Cyril Brulebois wrote:
> Florian Fainelli <f.fainelli@gmail.com> (2022-05-11):
>> How about we get a chance to fix this? Where, when and how was this even
>> reported?
> 
> I started downstream:
>    https://bugs.debian.org/1010365
> 
> did some more debugging and moved upstream (the link is mentioned in
> each commit message) roughly 10 days ago:
>    https://bugzilla.kernel.org/show_bug.cgi?id=215925
> 
> As I wrote in response to Thorsten Leemhuis (regressions@), who looped
> in a bunch of people:
> 
>     I had spent so much time bisecting that issue that I concentrated on
>     trying to summarize it properly in Bugzilla, failing to check
>     reporting guidelines and best practices (I even missed the
>     Regression: yes flag in my initial submission).
> 
> Again, sorry for failing to notify everyone in the first place, I tried
> to have the contents of the report squared away.
> 
> That being said, as mentioned on regressions@ & linux-pci@, I'm happy to
> test any attempts at fixing the issue, instead of a full-on revert. I'll
> also try to track mainline more closely, so that such obvious issues
> don't go unnoticed for ~1.5 release cycles.

No worries, I don't have a CM4 board at the moment but will try to order 
one so we can get to the bottom of this quicker.
-- 
Florian

  reply	other threads:[~2022-05-11 20:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11 20:18 [PATCH 0/4] PCI: brcmstb: Revert subdevice regulator stuff Bjorn Helgaas
2022-05-11 20:18 ` [PATCH 1/4] Revert "PCI: brcmstb: Do not turn off WOL regulators on suspend" Bjorn Helgaas
2022-05-12  6:24   ` Thorsten Leemhuis
2022-05-12 12:45     ` Bjorn Helgaas
2022-05-11 20:18 ` [PATCH 2/4] Revert "PCI: brcmstb: Add control of subdevice voltage regulators" Bjorn Helgaas
2022-05-11 20:18 ` [PATCH 3/4] Revert "PCI: brcmstb: Add mechanism to turn on subdev regulators" Bjorn Helgaas
2022-05-11 20:18 ` [PATCH 4/4] Revert "PCI: brcmstb: Split brcm_pcie_setup() into two funcs" Bjorn Helgaas
2022-05-11 20:24 ` [PATCH 0/4] PCI: brcmstb: Revert subdevice regulator stuff Florian Fainelli
2022-05-11 20:39   ` Cyril Brulebois
2022-05-11 20:54     ` Florian Fainelli [this message]
2022-05-11 20:39   ` Bjorn Helgaas
2022-06-13 17:06     ` Florian Fainelli
2022-06-14  0:00       ` Bjorn Helgaas
2022-06-14 16:16         ` Florian Fainelli
2022-06-14 18:59         ` Jim Quinlan
2022-06-21 23:32           ` Bjorn Helgaas
2022-06-27 23:18             ` Bjorn Helgaas
2022-07-01 11:25               ` Jim Quinlan

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=aaa4b4d5-486d-869c-10b7-f88c87c450fd@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=bhelgaas@google.com \
    --cc=helgaas@kernel.org \
    --cc=jim2101024@gmail.com \
    --cc=kibi@debian.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=nsaenz@kernel.org \
    --cc=regressions@lists.linux.dev \
    /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.