From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/4] bcm2835-dt-64-next-2017-06-08
Date: Tue, 13 Jun 2017 12:41:00 -0700 [thread overview]
Message-ID: <ce06aff6-ef2b-0d6f-1aaf-dfc55dacf11f@gmail.com> (raw)
In-Reply-To: <20170613174356.22426-4-eric@anholt.net>
On 06/13/2017 10:43 AM, Eric Anholt wrote:
> Hi Florian,
>
> Here's the last pull request in this series. I've based this summary
> on the bcm2835-dt-next tag, to clarify what's in this patch series,
> but it does require being careful since it involves a cross-merge
> between branches.
Merged, thanks, I will make sure this is also promoted to my pull
request tag.
Thanks!
--
Florian
next prev parent reply other threads:[~2017-06-13 19:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 17:43 [GIT PULL 1/4] bcm2835-defconfig-next-2017-06-12 Eric Anholt
2017-06-13 17:43 ` [GIT PULL 2/4] bcm2835-maintainers-next-2017-06-08 Eric Anholt
2017-06-13 19:39 ` Florian Fainelli
2017-06-13 17:43 ` [GIT PULL 3/4] bcm2835-dt-next-2017-06-12 Eric Anholt
2017-06-13 19:39 ` Florian Fainelli
2017-06-13 17:43 ` [GIT PULL 4/4] bcm2835-dt-64-next-2017-06-08 Eric Anholt
2017-06-13 19:41 ` Florian Fainelli [this message]
2017-06-13 19:37 ` [GIT PULL 1/4] bcm2835-defconfig-next-2017-06-12 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=ce06aff6-ef2b-0d6f-1aaf-dfc55dacf11f@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).