From: William Zhang <william.zhang@broadcom.com>
To: U-Boot Mailing List <u-boot@lists.denx.de>,
anand.gore@broadcom.com, kursad.oney@broadcom.com,
noltari@gmail.com, philippe.reynes@softathome.com,
tomer.yacoby@broadcom.com, dregan@mail.com
Cc: William Zhang <william.zhang@broadcom.com>,
joel.peshkin@broadcom.com, dan.beygelman@broadcom.com
Subject: [PATCH v3 10/10] MAINTAINERS: Add Broadcom Broadband SoC HS SPI drivers
Date: Wed, 7 Jun 2023 16:37:10 -0700 [thread overview]
Message-ID: <20230607233710.3805-11-william.zhang@broadcom.com> (raw)
In-Reply-To: <20230607233710.3805-1-william.zhang@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
Add entry for Broadcom Broadband SoC HS SPI drivers
Signed-off-by: William Zhang <william.zhang@broadcom.com>
---
Changes in v3: None
Changes in v2:
- Add Álvaro Fernández Rojas as another maintainer
MAINTAINERS | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 228d8af433df..0ebeaee86b33 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -824,6 +824,15 @@ F: include/bootstd.h
F: net/eth_bootdevice.c
F: test/boot/
+BROADCOM Broadband SoC High Speed SPI Controller DRIVER
+M: William Zhang <william.zhang@broadcom.com>
+M: Kursad Oney <kursad.oney@broadcom.com>
+M: Álvaro Fernández Rojas <noltari@gmail.com>
+S: Maintained
+F: doc/device-tree-bindings/spi/brcm,bcm63xx-hsspi.yaml
+F: drivers/spi/bcm63xx_hsspi.c
+F: drivers/spi/bcmbca_hsspi.c
+
BTRFS
M: Marek Behún <kabel@kernel.org>
R: Qu Wenruo <wqu@suse.com>
--
2.37.3
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4212 bytes --]
next prev parent reply other threads:[~2023-06-07 23:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 23:37 [PATCH v3 00/10] spi: bcm63xx-hsspi: driver and doc updates William Zhang
2023-06-07 23:37 ` [PATCH v3 01/10] spi: bcm63xx-hsspi: Make driver depend on BCMBCA arch William Zhang
2023-06-11 10:39 ` Jagan Teki
2023-06-07 23:37 ` [PATCH v3 02/10] spi: bcm63xx-hsspi: Fix multi-bit mode setting William Zhang
2023-06-11 10:40 ` Jagan Teki
2023-06-07 23:37 ` [PATCH v3 03/10] spi: bcm63xx-hsspi: Add new compatible string support William Zhang
2023-06-11 10:41 ` Jagan Teki
2023-06-07 23:37 ` [PATCH v3 04/10] spi: bcm63xx-hsspi: Add prepend mode support William Zhang
2023-06-11 10:42 ` Jagan Teki
2023-06-07 23:37 ` [PATCH v3 05/10] spi: bcmbca-hsspi: Add driver for newer HSSPI controller William Zhang
2023-06-11 10:42 ` Jagan Teki
2023-06-07 23:37 ` [PATCH v3 06/10] dt-bindings: spi: Add bcm63xx-hsspi controller support William Zhang
2023-06-11 10:43 ` Jagan Teki
2023-06-14 19:59 ` William Zhang
2023-06-07 23:37 ` [PATCH v3 07/10] ARM: dts: broadcom: bcmbca: Add spi controller node William Zhang
2023-06-07 23:37 ` [PATCH v3 08/10] arm64: " William Zhang
2023-06-07 23:37 ` [PATCH v3 09/10] broadcom: bcmbca: Enable SPI drivers by default William Zhang
2023-06-07 23:37 ` William Zhang [this message]
2023-08-09 2:02 ` [PATCH v3 10/10] MAINTAINERS: Add Broadcom Broadband SoC HS SPI drivers Tom Rini
2023-08-11 23:57 ` William Zhang
2023-08-12 1:00 ` Tom Rini
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=20230607233710.3805-11-william.zhang@broadcom.com \
--to=william.zhang@broadcom.com \
--cc=anand.gore@broadcom.com \
--cc=dan.beygelman@broadcom.com \
--cc=dregan@mail.com \
--cc=joel.peshkin@broadcom.com \
--cc=kursad.oney@broadcom.com \
--cc=noltari@gmail.com \
--cc=philippe.reynes@softathome.com \
--cc=tomer.yacoby@broadcom.com \
--cc=u-boot@lists.denx.de \
/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