From: Florian Fainelli <f.fainelli@gmail.com>
To: soc@kernel.org
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
arnd@arndb.de, khilman@kernel.org,
bcm-kernel-feedback-list@broadcom.com, olof@lixom.net,
linux-arm-kernel@lists.infradead.org,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: [GIT PULL 1/2] Broadcom defconfig fixes for 5.6
Date: Fri, 28 Feb 2020 10:11:43 -0800 [thread overview]
Message-ID: <20200228181144.15148-1-f.fainelli@gmail.com> (raw)
The following changes since commit bb6d3fb354c5ee8d6bde2d576eb7220ea09862b9:
Linux 5.6-rc1 (2020-02-09 16:08:48 -0800)
are available in the Git repository at:
https://github.com/Broadcom/stblinux.git tags/arm-soc/for-5.6/defconfig-fixes
for you to fetch changes up to 653c00f289371fc5162f1daf4c3742113812aa94:
ARM: bcm2835_defconfig: Explicitly restore CONFIG_DEBUG_FS (2020-02-27 12:47:45 -0800)
----------------------------------------------------------------
This pull request contains Broadcom ARM-based SoCs defconfig file(s)
fixes for v5.6, please pull the following:
- Stefan restores CONFIG_DEBUG_FS from the bcm2835_defconfig which was
accidentally removed
----------------------------------------------------------------
Stefan Wahren (1):
ARM: bcm2835_defconfig: Explicitly restore CONFIG_DEBUG_FS
arch/arm/configs/bcm2835_defconfig | 1 +
1 file changed, 1 insertion(+)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-02-28 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 18:11 Florian Fainelli [this message]
2020-02-28 18:11 ` [GIT PULL 2/2] Broadcom devicetree fixes for 5.6 Florian Fainelli
2020-02-29 19:49 ` [GIT PULL 1/2] Broadcom defconfig " 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=20200228181144.15148-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=m.szyprowski@samsung.com \
--cc=olof@lixom.net \
--cc=soc@kernel.org \
--cc=stefan.wahren@i2se.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.