From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Fri, 12 Dec 2014 10:13:36 +0100 (CET) Received: from mailapp01.imgtec.com ([195.59.15.196]:27433 "EHLO mailapp01.imgtec.com" rhost-flags-OK-OK-OK-OK) by eddie.linux-mips.org with ESMTP id S27006871AbaLLJNeyhV7w (ORCPT ); Fri, 12 Dec 2014 10:13:34 +0100 Received: from KLMAIL01.kl.imgtec.org (unknown [192.168.5.35]) by Websense Email Security Gateway with ESMTPS id BB42934CFF29F for ; Fri, 12 Dec 2014 09:13:26 +0000 (GMT) Received: from LEMAIL01.le.imgtec.org (192.168.152.62) by KLMAIL01.kl.imgtec.org (192.168.5.35) with Microsoft SMTP Server (TLS) id 14.3.195.1; Fri, 12 Dec 2014 09:13:28 +0000 Received: from [192.168.154.56] (192.168.154.56) by LEMAIL01.le.imgtec.org (192.168.152.62) with Microsoft SMTP Server (TLS) id 14.3.210.2; Fri, 12 Dec 2014 09:13:28 +0000 Message-ID: <548AB1B8.7040503@imgtec.com> Date: Fri, 12 Dec 2014 09:13:28 +0000 From: Markos Chandras User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Subject: Re: MIPS in 3.19 References: <20141211132746.GF31723@linux-mips.org> <20141211212240.GA6477@linux-mips.org> <548A4ACC.9050106@gmail.com> In-Reply-To: <548A4ACC.9050106@gmail.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [192.168.154.56] Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 44627 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: Markos.Chandras@imgtec.com Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: linux-mips X-List-ID: linux-mips List-subscribe: List-owner: List-post: List-archive: X-list: linux-mips On 12/12/2014 01:54 AM, Florian Fainelli wrote: > On 11/12/14 13:22, Ralf Baechle wrote: >> On Thu, Dec 11, 2014 at 11:19:53AM -0800, Kevin Cernekee wrote: >> >>> On Thu, Dec 11, 2014 at 5:27 AM, Ralf Baechle wrote: >>>> >>>> Kevin Cernekee (15): >>>> Documentation: DT: Add entries for BCM3384 and its peripherals >>> >>>> MIPS: bcm3384: Initial commit of bcm3384 platform support >>>> MAINTAINERS: Add entry for BCM33xx cable chips >>> >>> Hi Ralf, >>> >>> Could we drop/revert these three patches for now, and then use the >>> "BMIPS Generic target V4" patch series to support BCM3384? The BMIPS >>> Generic series incorporates a great deal of helpful feedback from Arnd >>> and others, and it also runs on 5+ other chips. >>> >>> It is OK if it isn't merged until 3.20+. No rush. >> >> Too late - the pull request to Linus is out. > > Ralf, you applied the patches without email notice, Kevin asked you to > drop them way before sending a pull request while he was posting v2-3-4 > of his patch set, and now he has to deal with potential reverts, this is > counter productive. > > I do not see the MIPS pull request anywhere in public email archives, so > we could not even say "wait" before this went out to Linus. > -- > Florian > I am a little confused as well. Sometimes the pull requests appear on LMO, some other times they don't. Would it be possible to CC LMO every time a pull request is sent to Linus so we have time to review it (more pair of eyes is not a bad thing) and comment on it if needed? -- markos From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailapp01.imgtec.com ([195.59.15.196]:27433 "EHLO mailapp01.imgtec.com" rhost-flags-OK-OK-OK-OK) by eddie.linux-mips.org with ESMTP id S27006871AbaLLJNeyhV7w (ORCPT ); Fri, 12 Dec 2014 10:13:34 +0100 Received: from KLMAIL01.kl.imgtec.org (unknown [192.168.5.35]) by Websense Email Security Gateway with ESMTPS id BB42934CFF29F for ; Fri, 12 Dec 2014 09:13:26 +0000 (GMT) Message-ID: <548AB1B8.7040503@imgtec.com> Date: Fri, 12 Dec 2014 09:13:28 +0000 From: Markos Chandras MIME-Version: 1.0 Subject: Re: MIPS in 3.19 References: <20141211132746.GF31723@linux-mips.org> <20141211212240.GA6477@linux-mips.org> <548A4ACC.9050106@gmail.com> In-Reply-To: <548A4ACC.9050106@gmail.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Return-Path: Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-subscribe: List-owner: List-post: List-archive: To: linux-mips@linux-mips.org Message-ID: <20141212091328.e9rt8VcBPMfwMPsKVl46Nvr1THX3nrIuGFkho65GlAQ@z> On 12/12/2014 01:54 AM, Florian Fainelli wrote: > On 11/12/14 13:22, Ralf Baechle wrote: >> On Thu, Dec 11, 2014 at 11:19:53AM -0800, Kevin Cernekee wrote: >> >>> On Thu, Dec 11, 2014 at 5:27 AM, Ralf Baechle wrote: >>>> >>>> Kevin Cernekee (15): >>>> Documentation: DT: Add entries for BCM3384 and its peripherals >>> >>>> MIPS: bcm3384: Initial commit of bcm3384 platform support >>>> MAINTAINERS: Add entry for BCM33xx cable chips >>> >>> Hi Ralf, >>> >>> Could we drop/revert these three patches for now, and then use the >>> "BMIPS Generic target V4" patch series to support BCM3384? The BMIPS >>> Generic series incorporates a great deal of helpful feedback from Arnd >>> and others, and it also runs on 5+ other chips. >>> >>> It is OK if it isn't merged until 3.20+. No rush. >> >> Too late - the pull request to Linus is out. > > Ralf, you applied the patches without email notice, Kevin asked you to > drop them way before sending a pull request while he was posting v2-3-4 > of his patch set, and now he has to deal with potential reverts, this is > counter productive. > > I do not see the MIPS pull request anywhere in public email archives, so > we could not even say "wait" before this went out to Linus. > -- > Florian > I am a little confused as well. Sometimes the pull requests appear on LMO, some other times they don't. Would it be possible to CC LMO every time a pull request is sent to Linus so we have time to review it (more pair of eyes is not a bad thing) and comment on it if needed? -- markos