U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: William Zhang <william.zhang@broadcom.com>
To: Tom Rini <trini@konsulko.com>
Cc: 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,
	joel.peshkin@broadcom.com, dan.beygelman@broadcom.com
Subject: Re: [PATCH v3 10/10] MAINTAINERS: Add Broadcom Broadband SoC HS SPI drivers
Date: Fri, 11 Aug 2023 16:57:10 -0700	[thread overview]
Message-ID: <36cbdb5d-f6a9-2829-a70f-1bc9a790cbf4@broadcom.com> (raw)
In-Reply-To: <20230809020256.GA2544948@bill-the-cat>

[-- Attachment #1: Type: text/plain, Size: 610 bytes --]

Hi Tom,

On 08/08/2023 07:02 PM, Tom Rini wrote:
> On Wed, Jun 07, 2023 at 04:37:10PM -0700, William Zhang wrote:
> 
>> Add entry for Broadcom Broadband SoC HS SPI drivers
>>
>> Signed-off-by: William Zhang <william.zhang@broadcom.com>
> 
> Can you please rebase this rest of this series on top of current next
> and fix the compiler warnings that show up, thanks.
> 
Sorry for the delay. I noticed that patch 1 to 6 in this series are 
already in u-boot/next. I did see compiler warning on bcm63xx_hsspi.c 
when build for arm64.  Should I just provide a new patch for this 
warning based on the current next?

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4212 bytes --]

  reply	other threads:[~2023-08-11 23:57 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 ` [PATCH v3 10/10] MAINTAINERS: Add Broadcom Broadband SoC HS SPI drivers William Zhang
2023-08-09  2:02   ` Tom Rini
2023-08-11 23:57     ` William Zhang [this message]
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=36cbdb5d-f6a9-2829-a70f-1bc9a790cbf4@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=trini@konsulko.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