linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: soc@kernel.org
Cc: William Zhang <william.zhang@broadcom.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Miaoqian Lin <linmq006@gmail.com>,
	linux-arm-kernel@lists.infradead.org, arnd@arndb.de,
	olof@lixom.net, khilman@kernel.org,
	bcm-kernel-feedback-list@broadcom.com
Subject: [GIT PULL 7/7] Broadcom soc changes for 5.20
Date: Mon, 11 Jul 2022 09:44:51 -0700	[thread overview]
Message-ID: <20220711164451.3542127-8-f.fainelli@gmail.com> (raw)
In-Reply-To: <20220711164451.3542127-1-f.fainelli@gmail.com>

The following changes since commit f2906aa863381afb0015a9eb7fefad885d4e5a56:

  Linux 5.19-rc1 (2022-06-05 17:18:54 -0700)

are available in the Git repository at:

  https://github.com/Broadcom/stblinux.git tags/arm-soc/for-5.20/soc

for you to fetch changes up to fa0ef5a086a05306fc5322bbda73459725eda923:

  ARM: debug: bcmbca: Replace ARCH_BCM_63XX with ARCH_BCMBCA (2022-07-08 14:08:51 -0700)

----------------------------------------------------------------
This pull request contains Broadcom SoC drivers changes for 5.20, please
pull the following:

- Miaoqian fixes a device_node reference count leak in the Kona SMC
  initialization code

- William moves the 63138 support code to use CONFIG_ARCH_BCMBCA which
  is how all of those similar SoCs from the BCA division are supported
  moving forward. This includes machine code and UART low-level debug
  code.

----------------------------------------------------------------
Miaoqian Lin (1):
      ARM: bcm: Fix refcount leak in bcm_kona_smc_init

William Zhang (3):
      arm: bcmbca: Move BCM63138 ARCH_BCM_63XX to ARCH_BCMBCA
      arm: bcmbca: Add BCMBCA sub platforms
      ARM: debug: bcmbca: Replace ARCH_BCM_63XX with ARCH_BCMBCA

 arch/arm/Kconfig.debug           |  2 +-
 arch/arm/mach-bcm/Kconfig        | 61 ++++++++++++++++++++++++++++------------
 arch/arm/mach-bcm/Makefile       | 11 ++++----
 arch/arm/mach-bcm/bcm63xx.c      | 27 ------------------
 arch/arm/mach-bcm/bcm_kona_smc.c |  1 +
 5 files changed, 50 insertions(+), 52 deletions(-)
 delete mode 100644 arch/arm/mach-bcm/bcm63xx.c

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2022-07-11 16:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11 16:44 [PATCH 0/7] Broadcom SoC updates for 5.20 Florian Fainelli
2022-07-11 16:44 ` [GIT PULL 1/7] Broadcom defconfig changes " Florian Fainelli
2022-07-11 16:44 ` [GIT PULL 2/7] Broadcom defconfig-arm64 " Florian Fainelli
2022-07-11 16:44 ` [GIT PULL 3/7] Broadcom devicetree " Florian Fainelli
2022-07-11 16:44 ` [GIT PULL 4/7] Broadcom devicetree-arm64 " Florian Fainelli
2022-07-11 16:44 ` [GIT PULL 5/7] Broadcom drivers " Florian Fainelli
2022-07-11 16:44 ` [GIT PULL 6/7] Broadcom maintainers " Florian Fainelli
2022-07-11 16:44 ` Florian Fainelli [this message]

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=20220711164451.3542127-8-f.fainelli@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=arnd@arndb.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=khilman@kernel.org \
    --cc=linmq006@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=olof@lixom.net \
    --cc=soc@kernel.org \
    --cc=william.zhang@broadcom.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).