linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] MAINTAINERS update for Broadcom SoCs for 4.1
Date: Mon, 13 Apr 2015 15:56:23 -0700	[thread overview]
Message-ID: <552C4997.8010403@gmail.com> (raw)
In-Reply-To: <201504140055.05789.arnd@arndb.de>

On 13/04/15 15:55, Arnd Bergmann wrote:
> On Friday 10 April 2015, Florian Fainelli wrote:
>> The following changes since commit f22e6e847115abc3a0e2ad7bb18d243d42275af1:
>>
>>   Linux 4.0-rc7 (2015-04-06 15:39:45 -0700)
>>
>> are available in the git repository at:
>>
>>   http://github.com/broadcom/stblinux tags/arm-soc/for-4.1/maintainers
>>
>> for you to fetch changes up to 90a604a9ce881290fdc7468df4ca4e9c2ae4de62:
>>
>>   MAINTAINERS: Update brcmstb entry (2015-04-10 11:52:40 -0700)
>>
>> ----------------------------------------------------------------
>> This pull request contains 3 changes to the MAINTAINERS file for Broadcom SoCs:
>>
>> - add Ray and Scott for mach-bcm
>> - remove Christian for mach-bcm
>> - remove Marc for brcmstb
> 
> I tried to pull these, but it would merge in 4.0-rc7, which I don't want to
> do at this point. I also tried to cherry-pick the changes into
> next/fixes-non-critical, which in turn conflicted with the earlier patch
> that removes Matt as a maintainer.

I used 4.0-rc7 since I knew for sure there was the removal of Matt's
entry, sorry about that.

> 
> Not worth trying anything fancy I think, please re-submit these based on
> 4.1-rc1.

Agreed, let's do this, thanks!
-- 
Florian

      reply	other threads:[~2015-04-13 22:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10 19:00 [GIT PULL] MAINTAINERS update for Broadcom SoCs for 4.1 Florian Fainelli
2015-04-13 22:55 ` Arnd Bergmann
2015-04-13 22:56   ` Florian Fainelli [this message]

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=552C4997.8010403@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).