From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] MAINTAINERS: update Broadcom Cygnus SoC git tree
Date: Thu, 29 Jan 2015 12:51:46 -0800 [thread overview]
Message-ID: <54CA9D62.2050908@gmail.com> (raw)
In-Reply-To: <54CA88F2.5080700@broadcom.com>
On 29/01/15 11:24, Ray Jui wrote:
>
>
> On 1/29/2015 11:01 AM, Dmitry Torokhov wrote:
>> On Fri, Jan 9, 2015 at 2:49 PM, Ray Jui <rjui@broadcom.com> wrote:
>>>
>>>
>>> On 1/9/2015 2:45 PM, Florian Fainelli wrote:
>>>> The Cygnus SoC git tree is moved from github.com/brcm/linux.git to its
>>>> own git tree at github.com/Broadcom/cygnus-linux.git.
>>>>
>>>> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
>>>> ---
>>>> MAINTAINERS | 2 +-
>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>>> index ff73215cd165..4a8f3459f9c2 100644
>>>> --- a/MAINTAINERS
>>>> +++ b/MAINTAINERS
>>>> @@ -2192,7 +2192,7 @@ M: Ray Jui <rjui@broadcom.com>
>>>> M: Scott Branden <sbranden@broadcom.com>
>>>> L: linux-arm-kernel at lists.infradead.org (moderated for non-subscribers)
>>>> L: bcm-kernel-feedback-list at broadcom.com
>>>> -T: git git://git.github.com/brcm/linux.git
>>>> +T: git git://git.github.com/Broadcom/cygnus-linux.git
>>>
>>> Looks fine to me!
>>
>> Hmm, the address does not work for me unless I drop 'git.' from the front:
>>
>> git://github.com/Broadcom/cygnus-linux.git
>>
>> Thanks.
>>
> Thanks, Dmitry.
>
> I just tried it myself and also got a connection timeout with
> git://git.github.com/Broadcom/cygnus-linux.git
>
> fatal: unable to connect to git.github.com:
> git.github.com[0: 23.235.47.133]: errno=Connection timed out
>
> Same issue for git://git.github.com/broadcom/stblinux.git and
> git://git.github.com/broadcom/arm-bcm63xx.git
>
> git://github.com/Broadcom/cygnus-linux.git works fine as you mentioned.
>
> Florian, I think we need to fix this. Thanks.
Thanks for noticing, somehow I copy/pasted the original entry for cygnus
which was not working either. A new pull request has been submitted,
let's see if we can it merged or if incremental fixes are needed.
--
Florian
next prev parent reply other threads:[~2015-01-29 20:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 22:45 [PATCH 0/4] MAINTAINERS: Broadcom github updates Florian Fainelli
2015-01-09 22:45 ` [PATCH 1/4] MAINTAINERS: move BCM63xx ARM-based SoCs git tree Florian Fainelli
2015-01-09 22:45 ` [PATCH 2/4] MAINTAINERS: update Broadcom Cygnus SoC " Florian Fainelli
2015-01-09 22:49 ` Ray Jui
2015-01-29 19:01 ` Dmitry Torokhov
2015-01-29 19:24 ` Ray Jui
2015-01-29 20:51 ` Florian Fainelli [this message]
2015-01-09 22:45 ` [PATCH 3/4] MAINTAINERS: add a git entry for BCM7xxx ARM-based SoCs Florian Fainelli
2015-01-09 22:45 ` [PATCH 4/4] MAINTAINERS: add a git entry for BMIPS-based BCM7xxx SoCs 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=54CA9D62.2050908@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).