From: Florian Fainelli <f.fainelli@gmail.com>
To: Eric Anholt <eric@anholt.net>, Lee Jones <lee@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Stephen Warren <swarren@wwwdotorg.org>,
Stefan Wahren <stefan.wahren@i2se.com>,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [GIT PULL 4/4] bcm2835 MAINTAINERS updates for 4.12
Date: Fri, 24 Mar 2017 10:15:41 -0700 [thread overview]
Message-ID: <2e0b486c-06da-e81d-4966-d6e838e5709a@gmail.com> (raw)
In-Reply-To: <20170321193952.10270-4-eric@anholt.net>
On 03/21/2017 12:39 PM, Eric Anholt wrote:
> Linux 4.11-rc1 (2017-03-05 12:59:56 -0800)
>
> are available in the git repository at:
>
> git://github.com/anholt/linux tags/bcm2835-maintainers-next-2017-03-21
>
> for you to fetch changes up to 346ab44e65ac0e9aa1cd70b910fe06f8feb151c4:
>
> MAINTAINERS: Add Stefan Wahren to bcm2835. (2017-03-06 09:03:28 -0800)
>
> ----------------------------------------------------------------
> This pull request updates the MAINTAINERS file for BCM283x for 4.12.
>
> ----------------------------------------------------------------
And... merged as well, thanks!
--
Florian
WARNING: multiple messages have this Message-ID (diff)
From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/4] bcm2835 MAINTAINERS updates for 4.12
Date: Fri, 24 Mar 2017 10:15:41 -0700 [thread overview]
Message-ID: <2e0b486c-06da-e81d-4966-d6e838e5709a@gmail.com> (raw)
In-Reply-To: <20170321193952.10270-4-eric@anholt.net>
On 03/21/2017 12:39 PM, Eric Anholt wrote:
> Linux 4.11-rc1 (2017-03-05 12:59:56 -0800)
>
> are available in the git repository at:
>
> git://github.com/anholt/linux tags/bcm2835-maintainers-next-2017-03-21
>
> for you to fetch changes up to 346ab44e65ac0e9aa1cd70b910fe06f8feb151c4:
>
> MAINTAINERS: Add Stefan Wahren to bcm2835. (2017-03-06 09:03:28 -0800)
>
> ----------------------------------------------------------------
> This pull request updates the MAINTAINERS file for BCM283x for 4.12.
>
> ----------------------------------------------------------------
And... merged as well, thanks!
--
Florian
next prev parent reply other threads:[~2017-03-24 17:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 19:39 [GIT PULL 1/4] bcm2835 arm DT updates for 4.12 Eric Anholt
2017-03-21 19:39 ` Eric Anholt
2017-03-21 19:39 ` [GIT PULL 2/4] bcm2835 arm defconfig " Eric Anholt
2017-03-21 19:39 ` Eric Anholt
2017-03-24 17:13 ` Florian Fainelli
2017-03-24 17:13 ` Florian Fainelli
2017-03-21 19:39 ` [GIT PULL 1/4] bcm2835 arm64 " Eric Anholt
2017-03-21 19:39 ` Eric Anholt
2017-03-24 17:14 ` Florian Fainelli
2017-03-24 17:14 ` Florian Fainelli
2017-03-21 19:39 ` [GIT PULL 4/4] bcm2835 MAINTAINERS " Eric Anholt
2017-03-21 19:39 ` Eric Anholt
2017-03-24 17:15 ` Florian Fainelli [this message]
2017-03-24 17:15 ` Florian Fainelli
2017-03-24 17:13 ` [GIT PULL 1/4] bcm2835 arm DT " Florian Fainelli
2017-03-24 17:13 ` Florian Fainelli
2017-03-24 22:25 ` Arnd Bergmann
2017-03-24 22:25 ` Arnd Bergmann
2017-03-25 11:03 ` Stefan Wahren
2017-03-25 11:03 ` Stefan Wahren
2017-03-27 14:21 ` Arnd Bergmann
2017-03-27 14:21 ` Arnd Bergmann
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=2e0b486c-06da-e81d-4966-d6e838e5709a@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=eric@anholt.net \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=stefan.wahren@i2se.com \
--cc=swarren@wwwdotorg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.