From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/2] Broadcom drivers changes for 4.20 part 2
Date: Tue, 13 Nov 2018 11:25:58 -0800 [thread overview]
Message-ID: <20181113192558.yswpk2l65t2cp4cb@localhost> (raw)
In-Reply-To: <20181105234831.30526-1-f.fainelli@gmail.com>
On Mon, Nov 05, 2018 at 03:48:30PM -0800, Florian Fainelli wrote:
> The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:
>
> Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)
>
> are available in the Git repository at:
>
> https://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.20/drivers-part2
>
> for you to fetch changes up to 0810d5cc29a1e4bb9e738a478b746aebf8dc1931:
>
> bus: brcmstb_gisb: simplify getting .driver_data (2018-11-05 12:37:22 -0800)
>
> ----------------------------------------------------------------
> This pull request contains Broadcom ARM/ARM64/MIPS SoCs drivers changes
> for 4.20:
>
> - Wolfram converts the Broadcom STB GISB bus arbiter driver to use
> dev_get_drvdata()
>
> - Florian fixes the kernel's re-entry point function when the kernel is
> built with CONFIG_THUMB2_KERNEL
Hi Florian,
Not sure if you inteded this for 4.20 or to queue for next merge window? Right
now we're in bugfixes/regressions only for 4.20, and the GISB patch seems to be
a cleanup/refactor.
-Olof
next prev parent reply other threads:[~2018-11-13 19:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 23:48 [GIT PULL 1/2] Broadcom drivers changes for 4.20 part 2 Florian Fainelli
2018-11-05 23:48 ` [GIT PULL 2/2] Broadcom maintainers " Florian Fainelli
2018-11-13 19:24 ` Olof Johansson
2018-11-13 19:25 ` Olof Johansson [this message]
2018-11-13 19:32 ` [GIT PULL 1/2] Broadcom drivers " Florian Fainelli
2018-11-13 19:34 ` Olof Johansson
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=20181113192558.yswpk2l65t2cp4cb@localhost \
--to=olof@lixom.net \
--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).