linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Stefan Wahren <wahrenst@gmx.net>,
	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-64-next-2019-08-15
Date: Thu, 15 Aug 2019 15:57:08 -0700	[thread overview]
Message-ID: <b56f3cf4-bf75-264f-14f2-fcd569ce4be1@gmail.com> (raw)
In-Reply-To: <1565894043-5249-3-git-send-email-wahrenst@gmx.net>

On 8/15/19 11:34 AM, Stefan Wahren wrote:
> Hi Florian,
> 
> The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b:
> 
>   Linus 5.3-rc1 (2019-07-21 14:05:38 -0700)
> 
> are available in the git repository at:
> 
>   git://github.com/anholt/linux tags/bcm2835-defconfig-64-next-2019-08-15
> 
> for you to fetch changes up to e2dd73ac4440f7143e990e76bad9a46dc63a5951:
> 
>   arm64: defconfig: enable cpufreq support for RPi3 (2019-07-23 23:17:09 +0200)
> 
> ----------------------------------------------------------------
> This pull request enables the new RPi cpufreq driver in the 64-bit
> defconfig.
> 
> ----------------------------------------------------------------

Merged into defconfig-arm64/next, thanks Stefan!
-- 
Florian

  reply	other threads:[~2019-08-15 22:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-15 18:34 [GIT PULL 1/3] bcm2835-dt-next-2019-08-15 Stefan Wahren
2019-08-15 18:34 ` [GIT PULL 2/3] bcm2835-defconfig-next-2019-08-15 Stefan Wahren
2019-08-15 22:56   ` Florian Fainelli
2019-08-15 18:34 ` [GIT PULL 3/3] bcm2835-defconfig-64-next-2019-08-15 Stefan Wahren
2019-08-15 22:57   ` Florian Fainelli [this message]
2019-08-15 22:56 ` [GIT PULL 1/3] bcm2835-dt-next-2019-08-15 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=b56f3cf4-bf75-264f-14f2-fcd569ce4be1@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=wahrenst@gmx.net \
    /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).