From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] MAINTAINERS: Update BCM281XX/BCM11XXX/BCM216XX entry
Date: Wed, 22 Jun 2016 19:54:01 -0700 [thread overview]
Message-ID: <576B4F49.6010502@gmail.com> (raw)
In-Reply-To: <CAMsMSK-_3LUUsmgW5FwkP8mLpGcRG_sdE3XfXRJt3Za3KDLpeg@mail.gmail.com>
Le 21/06/2016 09:07, Chris Brand a ?crit :
> On Tue, Jun 21, 2016 at 7:34 AM, Jon Mason <jon.mason@broadcom.com> wrote:
> [snip]
>>>
>>> Hmmm. We should probably add bcm23550 here, too.
>>
>> Sure, I'll be happy to ammend this patch to add "N: bcm23550",
>> which appears to cover all of the newly added files. Also, does it
>> make sense to add you to the list of maintainers above?
>
> I guess so, yes.
Do you have a specific email address that would you want to use?
--
Florian
next prev parent reply other threads:[~2016-06-23 2:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 21:07 [PATCH 0/4] MAINTAINERS: update BCM SoC entries Jon Mason
2016-06-20 21:07 ` Jon Mason
2016-06-20 21:07 ` [PATCH 1/4] MAINTAINERS: Fix nsp false-positives Jon Mason
2016-06-20 21:07 ` Jon Mason
2016-06-20 21:07 ` [PATCH 2/4] MAINTAINERS: Add NS2 entry Jon Mason
2016-06-20 21:07 ` Jon Mason
2016-06-20 21:07 ` [PATCH 3/4] MAINTAINERS: Update BCM63XX entry Jon Mason
2016-06-20 21:07 ` Jon Mason
2016-06-20 21:07 ` [PATCH 4/4] MAINTAINERS: Update BCM281XX/BCM11XXX/BCM216XX entry Jon Mason
2016-06-20 21:35 ` Chris Brand
2016-06-21 14:34 ` Jon Mason
2016-06-21 16:07 ` Chris Brand
2016-06-23 2:54 ` Florian Fainelli [this message]
2016-06-20 21:14 ` [PATCH 0/4] MAINTAINERS: update BCM SoC entries Scott Branden
2016-06-20 21:14 ` Scott Branden
2016-07-05 23:27 ` Florian Fainelli
2016-07-05 23:27 ` Florian Fainelli
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=576B4F49.6010502@gmail.com \
--to=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.