From: Florian Fainelli <f.fainelli@gmail.com>
To: Stefan Wahren <stefan.wahren@i2se.com>,
Florian Fainelli <f.fainelli@gmail.com>
Cc: Eric Anholt <eric@anholt.net>,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 3/3] bcm2835-defconfig-next-2018-09-09
Date: Thu, 13 Sep 2018 15:18:19 -0700 [thread overview]
Message-ID: <ec141825-3eb4-1cfa-7d72-f44346f0aa2a@gmail.com> (raw)
In-Reply-To: <1536817833-3900-3-git-send-email-stefan.wahren@i2se.com>
On 09/12/18 22:50, Stefan Wahren wrote:
> Hi Florian,
>
> The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
>
> Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
>
> are available in the git repository at:
>
> git://github.com/anholt/linux tags/bcm2835-defconfig-next-2018-09-09
>
> for you to fetch changes up to 99fa3b0c6082bff346f7d09f29e5edcc93d40bd3:
>
> ARM: bcm2835_defconfig: Enable bcm2835-audio (2018-09-02 18:49:33 +0200)
>
> ----------------------------------------------------------------
> This pull request brings enables the RPi audio driver in the
> bcm2835_defconfig.
>
> ----------------------------------------------------------------
Merged into defconfig/next, thanks Stefan!
--
Florian
next prev parent reply other threads:[~2018-09-13 22:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 5:50 [GIT PULL 1/3] bcm2835-dt-next-2018-09-09 Stefan Wahren
2018-09-13 5:50 ` [GIT PULL 2/3] bcm2835-dt-64-next-2018-09-09 Stefan Wahren
2018-09-13 22:18 ` Florian Fainelli
2018-09-13 5:50 ` [GIT PULL 3/3] bcm2835-defconfig-next-2018-09-09 Stefan Wahren
2018-09-13 22:18 ` Florian Fainelli [this message]
2018-09-13 22:17 ` [GIT PULL 1/3] bcm2835-dt-next-2018-09-09 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=ec141825-3eb4-1cfa-7d72-f44346f0aa2a@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=eric@anholt.net \
--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 \
/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).