From: Florian Fainelli <f.fainelli@gmail.com>
To: soc@kernel.org
Cc: William Zhang <william.zhang@broadcom.com>,
Florian Fainelli <f.fainelli@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 1/5] Broadcom defconfig-arm64 changes for 6.1
Date: Wed, 14 Sep 2022 19:30:40 -0700 [thread overview]
Message-ID: <20220915023044.2350782-1-f.fainelli@gmail.com> (raw)
The following changes since commit 568035b01cfb107af8d2e4bd2fb9aea22cf5b868:
Linux 6.0-rc1 (2022-08-14 15:50:18 -0700)
are available in the Git repository at:
https://github.com/Broadcom/stblinux.git tags/arm-soc/for-6.1/defconfig-arm64
for you to fetch changes up to d30b361310f808fbb5837edd598cb5aaa3fca737:
arm64: defconfig: remove BCM4908 (2022-08-15 09:57:58 -0700)
----------------------------------------------------------------
This pull request contains Broadcom ARM64 defconfig changes for 6.1,
please pull the following:
- William completes the removal of ARCH_BCM4908 by removing that Kconfig
entry from the defconfig since it is being deleted after having been
transitional through 6.0
----------------------------------------------------------------
William Zhang (1):
arm64: defconfig: remove BCM4908
arch/arm64/configs/defconfig | 1 -
1 file changed, 1 deletion(-)
next reply other threads:[~2022-09-15 2:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 2:30 Florian Fainelli [this message]
2022-09-15 2:30 ` [GIT PULL 2/5] Broadcom devicetree changes for 6.1 Florian Fainelli
2022-09-15 2:30 ` [GIT PULL 3/5] Broadcom devicetree-arm64 " Florian Fainelli
2022-09-15 2:30 ` [GIT PULL 4/5] Broadcom drivers " Florian Fainelli
2022-09-15 2:30 ` [GIT PULL 5/5] Broadcom maintainers " Florian Fainelli
2022-09-15 20:20 ` [GIT PULL 1/5] Broadcom defconfig-arm64 " patchwork-bot+linux-soc
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=20220915023044.2350782-1-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=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