From: Florian Fainelli <f.fainelli@gmail.com>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Florian Fainelli <f.fainelli@gmail.com>
Cc: 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 4/4] bcm2835-soc-next-2021-01-25
Date: Tue, 26 Jan 2021 09:58:13 -0800 [thread overview]
Message-ID: <f35b1dae-3073-0f13-c4c4-6ea2351feb7e@gmail.com> (raw)
In-Reply-To: <20210125210131.14969-4-nsaenzjulienne@suse.de>
On 1/25/2021 1:01 PM, Nicolas Saenz Julienne wrote:
> Hi Florian,
>
> The following changes since commit 5c8fe583cce542aa0b84adc939ce85293de36e5e:
>
> Linux 5.11-rc1 (2020-12-27 15:30:22 -0800)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/nsaenz/linux-rpi.git tags/bcm2835-soc-next-2021-01-25
>
> for you to fetch changes up to 5674e314e674d5a7c4d38d8e9beed14b91ef04d3:
>
> ARM: bcm: Select BRCMSTB_L2_IRQ for bcm2835 (2021-01-25 21:59:06 +0100)
>
> ----------------------------------------------------------------
> Select BRCMSTB_L2_IRQ as it's now used on Raspberry Pi 4
>
> ----------------------------------------------------------------
Merged into soc/next, thanks Nicolas!
--
Florian
next prev parent reply other threads:[~2021-01-26 18:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 21:01 [GIT PULL 1/4] bcm2835-dt-next-2021-01-25 Nicolas Saenz Julienne
2021-01-25 21:01 ` [GIT PULL 2/4] bcm2835-defconfig-next-2021-01-25 Nicolas Saenz Julienne
2021-01-26 17:57 ` Florian Fainelli
2021-01-25 21:01 ` [GIT PULL 3/4] bcm2835-defconfig-arm64-next-2021-01-25 Nicolas Saenz Julienne
2021-01-26 17:57 ` Florian Fainelli
2021-01-25 21:01 ` [GIT PULL 4/4] bcm2835-soc-next-2021-01-25 Nicolas Saenz Julienne
2021-01-26 17:58 ` Florian Fainelli [this message]
2021-01-26 17:57 ` [GIT PULL 1/4] bcm2835-dt-next-2021-01-25 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=f35b1dae-3073-0f13-c4c4-6ea2351feb7e@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=nsaenzjulienne@suse.de \
/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
all inboxes | Powered by JetHome®