From: Arnd Bergmann <arnd@kernel.org>
To: arm@kernel.org, soc@kernel.org, Linus Walleij <linus.walleij@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>, Kees Cook <keescook@chromium.org>,
Stephan Gerhold <stephan@gerhold.net>,
phone-devel@vger.kernel.org, Arnd Bergmann <arnd@kernel.org>,
linux-arm-kernel@lists.infradead.org, newbyte@disroot.org
Subject: Re: [PATCH] ARM: configs: Update u8500_defconfig
Date: Fri, 16 Jul 2021 23:24:48 +0200 [thread overview]
Message-ID: <162647049954.3478428.18046978019252393704.b4-ty@arndb.de> (raw)
In-Reply-To: <20210712085522.672482-1-linus.walleij@linaro.org>
From: Arnd Bergmann <arnd@arndb.de>
On Mon, 12 Jul 2021 10:55:22 +0200, Linus Walleij wrote:
> The platform lost the framebuffer due to a commit solving a
> circular dependency in v5.14-rc1, so add it back in by explicitly
> selecting the framebuffer.
>
> The U8500 has also gained a few systems using touchscreens from
> Cypress, Melfas and Zinitix so add these at the same time as
> we're updating the defconfig anyway.
Applied to arm/fixes, thanks!
[1/1] ARM: configs: Update u8500_defconfig
commit: 042f2e107a2ea34605b3793a88b11761afc8e8e0
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@kernel.org>
To: arm@kernel.org, soc@kernel.org, Linus Walleij <linus.walleij@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>, Kees Cook <keescook@chromium.org>,
Stephan Gerhold <stephan@gerhold.net>,
phone-devel@vger.kernel.org, Arnd Bergmann <arnd@kernel.org>,
linux-arm-kernel@lists.infradead.org, newbyte@disroot.org
Subject: Re: [PATCH] ARM: configs: Update u8500_defconfig
Date: Fri, 16 Jul 2021 23:24:48 +0200 [thread overview]
Message-ID: <162647049954.3478428.18046978019252393704.b4-ty@arndb.de> (raw)
Message-ID: <20210716212448.5qm6rJYTqQCVQEs0iEzovgRJuTLdvmXE0IFNQws9hFg@z> (raw)
In-Reply-To: <20210712085522.672482-1-linus.walleij@linaro.org>
From: Arnd Bergmann <arnd@arndb.de>
On Mon, 12 Jul 2021 10:55:22 +0200, Linus Walleij wrote:
> The platform lost the framebuffer due to a commit solving a
> circular dependency in v5.14-rc1, so add it back in by explicitly
> selecting the framebuffer.
>
> The U8500 has also gained a few systems using touchscreens from
> Cypress, Melfas and Zinitix so add these at the same time as
> we're updating the defconfig anyway.
Applied to arm/fixes, thanks!
[1/1] ARM: configs: Update u8500_defconfig
commit: 042f2e107a2ea34605b3793a88b11761afc8e8e0
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-07-16 21:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 8:55 [PATCH] ARM: configs: Update u8500_defconfig Linus Walleij
2021-07-12 8:55 ` Linus Walleij
2021-07-16 21:22 ` patchwork-bot+linux-soc
2021-07-16 21:24 ` Arnd Bergmann [this message]
2021-07-16 21:24 ` Arnd Bergmann
2023-04-05 10:54 [PATCH] ARM: configs: Update U8500 defconfig Linus Walleij
2023-04-05 10:54 ` Linus Walleij
2023-04-14 13:10 ` 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=162647049954.3478428.18046978019252393704.b4-ty@arndb.de \
--to=arnd@kernel.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=keescook@chromium.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=newbyte@disroot.org \
--cc=phone-devel@vger.kernel.org \
--cc=soc@kernel.org \
--cc=stephan@gerhold.net \
/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.