From: Felipe Balbi <balbi@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>,
Chunfeng Yun <chunfeng.yun@mediatek.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
alcooperx@gmail.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, swboyd@chromium.org,
bcm-kernel-feedback-list@broadcom.com, matthias.bgg@gmail.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] MAINTAINERS: Add entry for Broadcom BDC driver
Date: Thu, 24 Sep 2020 10:22:37 +0300 [thread overview]
Message-ID: <87o8lvej0i.fsf@kernel.org> (raw)
In-Reply-To: <87r1qrej20.fsf@kernel.org>
[-- Attachment #1.1: Type: text/plain, Size: 926 bytes --]
Felipe Balbi <balbi@kernel.org> writes:
> Greg KH <gregkh@linuxfoundation.org> writes:
>
>> On Thu, Sep 17, 2020 at 02:49:54PM +0800, Chunfeng Yun wrote:
>>> On Sun, 2020-09-06 at 12:55 -0700, Florian Fainelli wrote:
>>> >
>>> > On 7/9/2020 8:48 PM, Florian Fainelli wrote:
>>> > > The Broadcom BDC driver did not have a MAINTAINERS entry which made it
>>> > > escape review from Al and myself, add an entry so the relevant mailing
>>> > > lists and people are copied.
>>> > >
>>> > > Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
>>> >
>>> > This patch still does not seem to have been picked up (not seeing it in
>>> > linux-next), can this be applied so we have an accurate maintainer
>>> > information for this driver?
>>> Ping
>>
>> Felipe should have picked this up.
>>
>> If not, please resend it again and I can.
>
> Applied
scratch that, it's already in Linus'
--
balbi
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 857 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-09-24 7:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 3:48 [PATCH] MAINTAINERS: Add entry for Broadcom BDC driver Florian Fainelli
2020-08-19 19:42 ` Florian Fainelli
2020-09-06 19:55 ` Florian Fainelli
2020-09-17 6:49 ` Chunfeng Yun
2020-09-17 7:38 ` Greg KH
2020-09-24 7:21 ` Felipe Balbi
2020-09-24 7:22 ` Felipe Balbi [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=87o8lvej0i.fsf@kernel.org \
--to=balbi@kernel.org \
--cc=alcooperx@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=chunfeng.yun@mediatek.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=swboyd@chromium.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).