From: Bjorn Helgaas <helgaas@kernel.org>
To: Jim Quinlan <james.quinlan@broadcom.com>
Cc: "Jim Quinlan" <jim2101024@gmail.com>,
linux-pci@vger.kernel.org,
"Nicolas Saenz Julienne" <nsaenz@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Cyril Brulebois" <kibi@debian.org>,
"Phil Elwell" <phil@raspberrypi.com>,
bcm-kernel-feedback-list@broadcom.com,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"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>
Subject: Re: [PATCH v5 4/5] PCI: brcmstb: Don't assume 2711 bootloader leaves PERST# asserted
Date: Wed, 10 May 2023 18:21:31 -0500 [thread overview]
Message-ID: <ZFwm+7pteghO3YPX@bhelgaas> (raw)
In-Reply-To: <CA+-6iNyAd8V1kqnfef_ektizOME3_ENEKMYaC0Q_EVdOLvBRhA@mail.gmail.com>
On Wed, May 10, 2023 at 06:46:45PM -0400, Jim Quinlan wrote:
> On Wed, May 10, 2023 at 6:26 PM Bjorn Helgaas <helgaas@kernel.org> wrote:
> >
> > Re subject, what does the patch actually *do*?
> >
> > It looks like it "asserts PERST# on BCM2711", which I think would be
> > more informative than "don't assume 2711 bootloader leaves PERST#
> > asserted".
>
> Do you have any other feedback on the other commits? I can change the
> subject message as you like and the remove the stale footnote you and
> Cyril noticed, and submit V6.
Nope, and there's really no hurry. Trivial stuff like this can be easily
done when merging. I think two postings per week is plenty. Each new
posting takes work to look at, so it's a win to wait a bit and
accumulate non-trivial updates before reposting.
Bjorn
next prev parent reply other threads:[~2023-05-10 23:21 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 22:01 [PATCH v5 0/5] PCI: brcmstb: Configure appropriate HW CLKREQ# mode Jim Quinlan
2023-05-08 22:01 ` [PATCH v5 1/5] dt-bindings: PCI: brcmstb: Add brcm,enable-l1ss property Jim Quinlan
2023-08-23 7:43 ` Manivannan Sadhasivam
2023-08-23 7:43 ` Manivannan Sadhasivam
2023-08-23 13:09 ` Jim Quinlan
2023-08-23 18:16 ` Manivannan Sadhasivam
2023-08-23 18:16 ` Manivannan Sadhasivam
2023-08-24 10:12 ` Lorenzo Pieralisi
2023-08-24 10:12 ` Lorenzo Pieralisi
2023-08-24 14:55 ` Jim Quinlan
2023-08-24 14:55 ` Jim Quinlan
2023-08-25 6:45 ` Manivannan Sadhasivam
2023-08-25 6:45 ` Manivannan Sadhasivam
2023-08-25 18:16 ` Jim Quinlan
2023-08-25 18:16 ` Jim Quinlan
2023-08-29 12:22 ` Rob Herring
2023-08-29 12:22 ` Rob Herring
2023-08-29 14:46 ` Manivannan Sadhasivam
2023-08-29 14:46 ` Manivannan Sadhasivam
2023-05-08 22:01 ` [PATCH v5 2/5] PCI: brcmstb: Configure HW CLKREQ# mode appropriate for downstream device Jim Quinlan
2023-05-08 22:01 ` [PATCH v5 3/5] PCI: brcmstb: Set higher value for internal bus timeout Jim Quinlan
2023-05-08 22:01 ` [PATCH v5 4/5] PCI: brcmstb: Don't assume 2711 bootloader leaves PERST# asserted Jim Quinlan
2023-05-09 7:51 ` Cyril Brulebois
2023-05-09 11:19 ` Jim Quinlan
2023-05-10 22:26 ` Bjorn Helgaas
2023-05-10 22:27 ` Bjorn Helgaas
2023-05-10 22:46 ` Jim Quinlan
2023-05-10 23:21 ` Bjorn Helgaas [this message]
2023-05-08 22:01 ` [PATCH v5 5/5] PCI: brcmstb: Remove stale comment Jim Quinlan
2023-05-08 22:02 ` Florian Fainelli
2023-05-09 7:46 ` [PATCH v5 0/5] PCI: brcmstb: Configure appropriate HW CLKREQ# mode Cyril Brulebois
2023-05-09 11:22 ` 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=ZFwm+7pteghO3YPX@bhelgaas \
--to=helgaas@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=f.fainelli@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-rpi-kernel@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=lpieralisi@kernel.org \
--cc=nsaenz@kernel.org \
--cc=phil@raspberrypi.com \
--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.