From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/2] Broadcom dts changes for 4.11 (part 2)
Date: Wed, 1 Feb 2017 18:06:41 -0800 [thread overview]
Message-ID: <d8915ae3-03fd-ee21-ad1c-082b407aebbd@gmail.com> (raw)
In-Reply-To: <20170202020420.31512-1-f.fainelli@gmail.com>
On 02/01/2017 06:04 PM, Florian Fainelli wrote:
> The following changes since commit c5a8e3add28ca4063410353acfbe6e650174e432:
>
> Merge tag 'bcm2835-dt-next-2017-01-17' into devicetree/next (2017-01-18 17:20:32 -0800)
>
> are available in the git repository at:
>
> http://github.com/Broadcom/stblinux devicetree/next
>
> for you to fetch changes up to c206e53d4c672ec83a4fc4d70eeac22d4b4ca80d:
>
> Merge tag 'bcm2835-dt-next-2017-01-31' into devicetree/next (2017-02-01 17:37:59 -0800)
Whoops ignore that email, the proper one has just been resent.
--
Florian
next prev parent reply other threads:[~2017-02-02 2:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 2:04 [GIT PULL 1/2] Broadcom dts changes for 4.11 (part 2) Florian Fainelli
2017-02-02 2:04 ` [GIT PULL 2/2] Broadcom maintainers changes for 4.11 Florian Fainelli
2017-02-07 16:17 ` Arnd Bergmann
2017-02-02 2:06 ` Florian Fainelli [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-02 2:06 [GIT PULL 1/2] Broadcom dts changes for 4.11 (part 2) Florian Fainelli
2017-02-07 14:49 ` Arnd Bergmann
2017-02-07 20:59 ` Florian Fainelli
2017-02-07 21:12 ` Arnd Bergmann
2017-02-07 23:52 ` Eric Anholt
2017-02-08 9:01 ` Arnd Bergmann
2017-02-09 19:16 ` Florian Fainelli
2017-02-07 21:05 ` Eric Anholt
2017-03-06 4:29 ` Baruch Siach
2017-03-06 6:21 ` 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=d8915ae3-03fd-ee21-ad1c-082b407aebbd@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).