From: Markos Chandras <Markos.Chandras@imgtec.com>
To: <linux-mips@linux-mips.org>
Subject: Re: MIPS in 3.19
Date: Fri, 12 Dec 2014 09:13:28 +0000 [thread overview]
Message-ID: <548AB1B8.7040503@imgtec.com> (raw)
In-Reply-To: <548A4ACC.9050106@gmail.com>
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 <ralf@linux-mips.org> 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
WARNING: multiple messages have this Message-ID (diff)
From: Markos Chandras <Markos.Chandras@imgtec.com>
To: linux-mips@linux-mips.org
Subject: Re: MIPS in 3.19
Date: Fri, 12 Dec 2014 09:13:28 +0000 [thread overview]
Message-ID: <548AB1B8.7040503@imgtec.com> (raw)
Message-ID: <20141212091328.e9rt8VcBPMfwMPsKVl46Nvr1THX3nrIuGFkho65GlAQ@z> (raw)
In-Reply-To: <548A4ACC.9050106@gmail.com>
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 <ralf@linux-mips.org> 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
next prev parent reply other threads:[~2014-12-12 9:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 13:27 MIPS in 3.19 Ralf Baechle
2014-12-11 19:19 ` Kevin Cernekee
2014-12-11 21:22 ` Ralf Baechle
2014-12-12 1:54 ` Florian Fainelli
2014-12-12 9:13 ` Markos Chandras [this message]
2014-12-12 9:13 ` Markos Chandras
2014-12-12 14:22 ` Ralf Baechle
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=548AB1B8.7040503@imgtec.com \
--to=markos.chandras@imgtec.com \
--cc=linux-mips@linux-mips.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