From: Matthias Brugger <matthias.bgg@gmail.com>
To: SoC Team <soc@kernel.org>, arm-soc <arm@kernel.org>
Cc: "moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Enric Balletbo Serra <eballetbo@gmail.com>
Subject: [GIT PULL] defconfig: mediatek: changes for v5.13
Date: Thu, 1 Apr 2021 15:58:41 +0200 [thread overview]
Message-ID: <70f6a2ae-2a99-6861-e591-9cc71bb174af@gmail.com> (raw)
Hi Arnd and Olof,
Please have a look at the following changes to defconfig. There is a small merge
conflict with the IMX branch, but it should be trivial.
Regards,
Matthias
---
The following changes since commit a38fd8748464831584a19438cbb3082b5a2dab15:
Linux 5.12-rc2 (2021-03-05 17:33:41 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git/
tags/v5.12-next-defconfig
for you to fetch changes up to f6dc45610879f88b1c37c07c8342f6764bcd55f4:
arm64: defconfig: Enable options to support panel display for Mediatek
Chromebooks (2021-03-31 12:12:59 +0200)
----------------------------------------------------------------
Enable option to boot MediaTek based chromebook (mt8173 and mt8183) with defconfig
----------------------------------------------------------------
Enric Balletbo i Serra (2):
arm64: defconfig: Allow mt8173-based boards to boot from usb
arm64: defconfig: Enable options to support panel display for Mediatek
Chromebooks
arch/arm64/configs/defconfig | 15 +++++++++++++++
1 file changed, 15 insertions(+)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-04-01 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 13:58 Matthias Brugger [this message]
2021-04-01 21:06 ` [GIT PULL] defconfig: mediatek: changes for v5.13 Arnd Bergmann
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=70f6a2ae-2a99-6861-e591-9cc71bb174af@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=arm@kernel.org \
--cc=eballetbo@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=soc@kernel.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).