Message ID | 1466128575-5378-5-git-send-email-f.fainelli@gmail.com |
---|---|
State | New |
Headers | show |
On Thu, Jun 16, 2016 at 06:56:13PM -0700, Florian Fainelli wrote: > The following changes since commit 1a695a905c18548062509178b98bc91e67510864: > > Linux 4.7-rc1 (2016-05-29 09:29:24 -0700) > > are available in the git repository at: > > http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.8/maintainers > > for you to fetch changes up to f6d925c8f8bb2e01c16dd5cd0e3d773beb84554d: > > MAINTAINERS: Update entry for BCM5301X ARM (2016-06-10 11:30:24 -0700) > > ---------------------------------------------------------------- > This pull request contains MAINTAINERS file updates for Broadcom SoCs: > > - Rafal updates the BCM5301x entry wih the typical Broadcom mailing-list > > ---------------------------------------------------------------- > Rafa?? Mi??ecki (1): > MAINTAINERS: Update entry for BCM5301X ARM Is bcm-kernel-feedback-list@broadcom.com a list that the public can subscribe to, or is it an internal list that the team is on? If it's the latter then it shouldn't be a mailing list in the maintainers file. There's a dual purpose to the L: entries -- one is where to cc the patches to, the other is what list to figure out how to subscribe to if you care about patches for that platform... Not merged until the above is clarified. -Olof
On 20 June 2016 at 07:51, Olof Johansson <olof@lixom.net> wrote: > On Thu, Jun 16, 2016 at 06:56:13PM -0700, Florian Fainelli wrote: >> The following changes since commit 1a695a905c18548062509178b98bc91e67510864: >> >> Linux 4.7-rc1 (2016-05-29 09:29:24 -0700) >> >> are available in the git repository at: >> >> http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.8/maintainers >> >> for you to fetch changes up to f6d925c8f8bb2e01c16dd5cd0e3d773beb84554d: >> >> MAINTAINERS: Update entry for BCM5301X ARM (2016-06-10 11:30:24 -0700) >> >> ---------------------------------------------------------------- >> This pull request contains MAINTAINERS file updates for Broadcom SoCs: >> >> - Rafal updates the BCM5301x entry wih the typical Broadcom mailing-list >> >> ---------------------------------------------------------------- >> Rafa?? Mi??ecki (1): >> MAINTAINERS: Update entry for BCM5301X ARM > > Is bcm-kernel-feedback-list@broadcom.com a list that the public can subscribe > to, or is it an internal list that the team is on? > > If it's the latter then it shouldn't be a mailing list in the maintainers > file. There's a dual purpose to the L: entries -- one is where to cc the > patches to, the other is what list to figure out how to subscribe to if you > care about patches for that platform... > > Not merged until the above is clarified. 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@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?
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@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@kernel.org, Dept-GELinuxNICDev@qlogic.com, linux-wimax@intel.com, ...). Arnd
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@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@kernel.org, > Dept-GELinuxNICDev@qlogic.com, linux-wimax@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. -Olof
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@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@kernel.org, >> Dept-GELinuxNICDev@qlogic.com, linux-wimax@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