From: scott.branden@broadcom•com (Scott Branden)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL 5/7] Broadcom maintainers changes for 4.8 Part 1
Date: Mon, 20 Jun 2016 14:33:31 -0700 [thread overview]
Message-ID: <5768612B.1010507@broadcom.com> (raw)
In-Reply-To: <CAOesGMgAM3MW0ha07HNbBz-QsXwWU=GU8pd6L-HdZ2gJ0Gp4Yw@mail.gmail.com>
Hi Olof/Rafal
On 16-06-20 08:30 AM, Olof Johansson wrote:
> On Mon, Jun 20, 2016 at 12:47 AM, Arnd Bergmann <arnd@arndb•de> wrote:
>> On Monday, June 20, 2016 9:35:53 AM CEST Rafa? Mi?ecki wrote:
>>>
>>> I was asked by Florian to add bcm-kernel-feedback-list@ but indeed he
>>> didn't specify if this should be L: entry.
>>> [21:24:43] <[florian]> rmilecki: also submit a patch that includes
>>> bcm-kernel-feedback-list at broadcom.com in the MAINTAINERS file for
>>> BCM5310X
>>> [21:36:51] <rmilecki> [florian]: I wasn't sure if I'm supposed to do that
>>> [21:36:53] <rmilecki> i can try I guess
>>>
>>> I'm afraid this mailing list is closed. Would M: entry work for it?
>>
>>
>> I think M: is better, we have a couple of examples like that (x86 at kernel.org,
>> Dept-GELinuxNICDev at qlogic.com, linux-wimax at intel.com, ...).
>
> Yep, having it as a M: entry would be fine with me as well. Please
> respin the patch/branch -- we can apply a patch directly instead of
> doing a merge if that's easier for you.
If M: is supposed to be used for bcm-kernel-feedback-list then a new
patch applied to multiple locations in the MAINTAINERS file would solve
the problem.
>
>
> -Olof
>
Regards,
Scott
next prev parent reply other threads:[~2016-06-20 21:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 1:56 [GIT PULL 1/7] Broadcom soc changes for 4.8 Part 1 Florian Fainelli
2016-06-17 1:56 ` [GIT PULL 2/7] Broadcom soc-arm64 " Florian Fainelli
2016-06-20 5:44 ` Olof Johansson
2016-06-17 1:56 ` [GIT PULL 3/7] Broadcom devicetree " Florian Fainelli
2016-06-20 5:45 ` Olof Johansson
2016-06-17 1:56 ` [GIT PULL 4/7] Broadcom devicetree-arm64 " Florian Fainelli
2016-06-20 5:48 ` Olof Johansson
2016-06-17 1:56 ` [GIT PULL 5/7] Broadcom maintainers " Florian Fainelli
2016-06-20 5:51 ` Olof Johansson
2016-06-20 7:35 ` Rafał Miłecki
2016-06-20 7:47 ` Arnd Bergmann
2016-06-20 15:30 ` Olof Johansson
2016-06-20 21:33 ` Scott Branden [this message]
2016-06-17 1:56 ` [GIT PULL 6/7] Broadcom defconfig " Florian Fainelli
2016-06-20 5:54 ` Olof Johansson
2016-06-20 21:43 ` Scott Branden
2016-06-20 21:51 ` Florian Fainelli
2016-06-20 22:04 ` Olof Johansson
2016-06-20 22:25 ` Scott Branden
2016-06-17 1:56 ` [GIT PULL 7/7] Broadcom drivers " Florian Fainelli
2016-06-20 5:55 ` Olof Johansson
2016-06-20 5:43 ` [GIT PULL 1/7] Broadcom soc " Olof Johansson
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=5768612B.1010507@broadcom.com \
--to=scott.branden@broadcom$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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