mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: William Zhang <william.zhang@broadcom.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
	Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>
Cc: dan.beygelman@broadcom.com, kursad.oney@broadcom.com,
	joel.peshkin@broadcom.com, anand.gore@broadcom.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: brcmnand: update STB BRCMNAND driver maintainer
Date: Tue, 12 Jul 2022 12:10:08 -0700	[thread overview]
Message-ID: <ec944386-5f24-ca6a-ab1c-644f7ac990f0@broadcom.com> (raw)
In-Reply-To: <12bad174-561f-87d4-ba3f-273ef2744843@gmail.com>

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



On 7/12/22 11:44, Florian Fainelli wrote:
> On 7/12/22 11:18, William Zhang wrote:
>> As the BCMBCA chip uses the same nand controller as STB chip and I
>> have been working on this driver internally in Broadcom, I'd like
>> to join the maintainer group of this driver and expect to contribute
>> changes to support BCMBCA chips, general driver changes and review
>> incoming patches as well.
>>
>> Signed-off-by: William Zhang <william.zhang@broadcom.com>
> 
> Acked-by: Florian Fainelli <f.fainelli@gmail.com>
> 
> While at it, we could probably rename the entry to: BROADCOM NAND FLASH 
> DRIVER since this controller is pretty much ubiquitous in all of what 
> Broadcom did produce that runs Linux, that is, it was not STB specific 
> very long.
Sounds good.  Will update that as well.

> 
> Thanks for stepping in!

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

      reply	other threads:[~2022-07-12 19:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 18:18 William Zhang
2022-07-12 18:44 ` Florian Fainelli
2022-07-12 19:10   ` William Zhang [this message]

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=ec944386-5f24-ca6a-ab1c-644f7ac990f0@broadcom.com \
    --to=william.zhang@broadcom.com \
    --cc=anand.gore@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=dan.beygelman@broadcom.com \
    --cc=f.fainelli@gmail.com \
    --cc=joel.peshkin@broadcom.com \
    --cc=kursad.oney@broadcom.com \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®