From: Jim Quinlan <james.quinlan@broadcom.com>
To: linux-pci@vger.kernel.org,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
bcm-kernel-feedback-list@broadcom.com, jim2101024@gmail.com,
james.quinlan@broadcom.com
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
FLATTENED DEVICE TREE BINDINGS),
linux-arm-kernel@lists.infradead.org (moderated list:BROADCOM
BCM7XXX ARM ARCHITECTURE),
linux-kernel@vger.kernel.org (open list),
linux-rpi-kernel@lists.infradead.org (moderated list:BROADCOM
BCM2711/BCM2835 ARM ARCHITECTURE)
Subject: [PATCH 0/1] RFC: Need feedback on PCI dt binding property
Date: Fri, 18 Oct 2024 14:22:44 -0400 [thread overview]
Message-ID: <20241018182247.41130-1-james.quinlan@broadcom.com> (raw)
We'd like to get early feedback on a dt binding property. We cannot
submit the code with it as there is a backlog of commits that must
be submitted first. We are just looking for some initial comments.
Jim Quinlan (1):
RFC: dt bindings: Add property "brcm,gen3-eq-presets"
.../devicetree/bindings/pci/brcm,stb-pcie.yaml | 12 ++++++++++++
1 file changed, 12 insertions(+)
--
2.43.0
next reply other threads:[~2024-10-18 18:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 18:22 Jim Quinlan [this message]
2024-10-18 18:22 ` [PATCH 1/1] RFC: dt bindings: Add property "brcm,gen3-eq-presets" Jim Quinlan
2024-10-18 19:03 ` Bjorn Helgaas
2024-10-21 19:03 ` Rob Herring
2024-10-25 1:08 ` Krishna Chaitanya Chundru
2024-10-28 18:51 ` James Quinlan
2024-10-29 5:17 ` Krishna Chaitanya Chundru
2024-10-29 14:22 ` Jim Quinlan
2024-10-29 14:48 ` Bjorn Helgaas
2024-10-29 15:22 ` Krishna Chaitanya Chundru
2024-10-29 15:40 ` Bjorn Helgaas
2024-10-29 15:55 ` Bjorn Helgaas
2024-10-29 16:54 ` Krishna Chaitanya Chundru
2024-10-29 17:34 ` Bjorn Helgaas
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=20241018182247.41130-1-james.quinlan@broadcom.com \
--to=james.quinlan@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=jim2101024@gmail.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=manivannan.sadhasivam@linaro.org \
--cc=nsaenz@kernel.org \
--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 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).