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 2/2] bcm2835-defconfig-next-2018-02-28
Date: Wed, 28 Feb 2018 15:37:27 -0800	[thread overview]
Message-ID: <cf9c863a-8523-00da-4399-d4be641ad96d@gmail.com> (raw)
In-Reply-To: <20180228213945.6781-2-eric@anholt.net>

On 02/28/2018 01:39 PM, Eric Anholt wrote:
> Hi Florian,
> 
>   Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
> 
> are available in the Git repository at:
> 
>   git://github.com/anholt/linux tags/bcm2835-defconfig-next-2018-02-28
> 
> for you to fetch changes up to bb9d91a4e5c87cabfa2c9d35761374aa11150c2d:
> 
>   ARM: multi_v7_defconfig: Enable thermal driver for RPi 2/3 (2018-02-26 15:30:43 -0800)
> 
> ----------------------------------------------------------------
> This pull request enables several recent drivers for the Raspberry Pi
> family in the defconfigs (thermal, BT, aux serial).
> 
> ----------------------------------------------------------------
> Stefan Wahren (2):
>       ARM: bcm2385_defconfig: Enable BT support for BCM43438
>       ARM: multi_v7_defconfig: Enable thermal driver for RPi 2/3
> 
> Tuomas Tynkkynen (1):
>       ARM: multi_v7_defconfig: Enable serial console on RPi 3

Merged into defconfig/next, thanks Eric.
-- 
Florian

  reply	other threads:[~2018-02-28 23:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-28 21:39 [GIT PULL 1/2] bcm2835-dt-next-2018-02-28 Eric Anholt
2018-02-28 21:39 ` [GIT PULL 2/2] bcm2835-defconfig-next-2018-02-28 Eric Anholt
2018-02-28 23:37   ` Florian Fainelli [this message]
2018-02-28 23:35 ` [GIT PULL 1/2] bcm2835-dt-next-2018-02-28 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=cf9c863a-8523-00da-4399-d4be641ad96d@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).