From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3.18] ARM: BCM: Broadcom BCM63138 support
Date: Sat, 06 Sep 2014 10:55:13 -0700 [thread overview]
Message-ID: <540B4A81.6080403@gmail.com> (raw)
In-Reply-To: <8641708.a9SSBxeRCZ@wuerfel>
On 09/06/14 07:33, Arnd Bergmann wrote:
> On Friday 05 September 2014 14:44:35 Florian Fainelli wrote:
>> Arnd, Olof,
>>
>> This pull request contains the basic Broadcom BCM63138 DSL SoC support
>> that has been posted a few weeks ago. Arnd has reviewed those changes, and
>> I was expecting Matt to carry these changes for me, but I did not get an
>> answer so far and I don't want these patches to be held much longer.
>
> You still need to take him on Cc at least. It's bad if Matt doesn't reply
> to your emails, but that's no excuse to send a pull request without giving
> him a chance to Ack or Nack it.
>
> Did you try contacting him on IRC? According to my logs, he was on #armlinux
> at the time you sent the pull request, although he's marked as idle now.
I have, but did not get an answer so far.
>
> Let's give Matt and Christian a few more days to reply, we can take the
> pull request if there is no reaction.
Works for me. We might want to come up with a different strategy for
handling mach-bcm stuff in the future, the BCM_MOBILE code will most
likely not be the highest activity.
Thanks
--
Florian
next prev parent reply other threads:[~2014-09-06 17:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 21:44 [GIT PULL 3.18] ARM: BCM: Broadcom BCM63138 support Florian Fainelli
2014-09-06 14:33 ` Arnd Bergmann
2014-09-06 17:55 ` Florian Fainelli [this message]
2014-09-15 4:56 ` Christian Daudt
2014-09-15 5:16 ` Florian Fainelli
2014-09-15 7:14 ` Christian Daudt
2014-09-16 16:27 ` Arnd Bergmann
2014-09-16 19:09 ` 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=540B4A81.6080403@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).