From: Florian Fainelli <f.fainelli@gmail.com>
To: Michael Chan <michael.chan@broadcom.com>
Cc: Netdev <netdev@vger.kernel.org>,
"Rafał Miłecki" <zajec5@gmail.com>,
andy@kernel.org
Subject: Re: [PATCH] MAINTAINERS: Update BNXT entry with firmware files
Date: Wed, 27 Apr 2022 09:32:37 -0700 [thread overview]
Message-ID: <5fa9f853-962e-784f-772c-7cbe61f38eec@gmail.com> (raw)
In-Reply-To: <CACKFLi=Zg54Uaewkrn9J9wBT3-ucCCJbPu=yXc61PTs=SDkTkQ@mail.gmail.com>
On 4/27/22 09:29, Michael Chan wrote:
> On Wed, Apr 27, 2022 at 9:21 AM Florian Fainelli <f.fainelli@gmail.com> wrote:
>>
>> There appears to be a maintainer gap for BNXT TEE firmware files which
>> causes some patches to be missed. Update the entry for the BNXT Ethernet
>> controller with its companion firmware files.
>>
>> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
>> ---
>> MAINTAINERS | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index f585242da63d..0316d0c9a908 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -3927,7 +3927,9 @@ BROADCOM BNXT_EN 50 GIGABIT ETHERNET DRIVER
>> M: Michael Chan <michael.chan@broadcom.com>
>> L: netdev@vger.kernel.org
>> S: Supported
>> +F: drivers/firmware/broadcom/tee_bnxt_fw.c
>> F: drivers/net/ethernet/broadcom/bnxt/
>> +F: linux/firmware/broadcom/tee_bnxt_fw.h
>
> should be include/linux/firmware/...
Meh, I copy/pasted without adding it, thanks Michael, does that mean you
are ok with being copied on those file changes?
--
Florian
next prev parent reply other threads:[~2022-04-27 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 16:21 [PATCH] MAINTAINERS: Update BNXT entry with firmware files Florian Fainelli
2022-04-27 16:29 ` Michael Chan
2022-04-27 16:32 ` Florian Fainelli [this message]
2022-04-27 16:34 ` Michael Chan
2022-04-27 16:32 ` Andy Shevchenko
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=5fa9f853-962e-784f-772c-7cbe61f38eec@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andy@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=zajec5@gmail.com \
/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