From: Kees Cook <keescook@chromium.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: arm@kernel.org, soc@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: configs: Update Versatile defconfig
Date: Wed, 14 Jul 2021 12:13:06 -0700 [thread overview]
Message-ID: <202107141212.757559237F@keescook> (raw)
In-Reply-To: <20210714081819.139210-1-linus.walleij@linaro.org>
On Wed, Jul 14, 2021 at 10:18:19AM +0200, Linus Walleij wrote:
> This updates the Versatile defconfig for the changes
> in the v5.14-rc1 kernel:
>
> - The Framebuffer CONFIG_FB needs to be explicitly selected
> or we don't get any framebuffer anymore. DRM has stopped to
> select FB because of circular dependency.
> - The CONFIG_FB_MODE_HELPERS are not needed when using DRM
> framebuffer emulation as DRM does.
> - The Acorn fonts are removed, the default framebuffer font
> works fine. I don't know why this was selected in the first
> place or how the Kconfig was altered so it was removed.
>
> Fixes: f611b1e7624c ("drm: Avoid circular dependencies for CONFIG_FB")
> Cc: Kees Cook <keescook@chromium.org>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Ah! Yes, thank you for catching these. :)
Reviewed-by: Kees Cook <keescook@chromium.org>
--
Kees Cook
WARNING: multiple messages have this Message-ID (diff)
From: Kees Cook <keescook@chromium.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: arm@kernel.org, soc@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: configs: Update Versatile defconfig
Date: Wed, 14 Jul 2021 12:13:06 -0700 [thread overview]
Message-ID: <202107141212.757559237F@keescook> (raw)
Message-ID: <20210714191306.BtyywAOf2ps7T4jzlZQMcjTVflKVxnXO3apUPZSlI30@z> (raw)
In-Reply-To: <20210714081819.139210-1-linus.walleij@linaro.org>
On Wed, Jul 14, 2021 at 10:18:19AM +0200, Linus Walleij wrote:
> This updates the Versatile defconfig for the changes
> in the v5.14-rc1 kernel:
>
> - The Framebuffer CONFIG_FB needs to be explicitly selected
> or we don't get any framebuffer anymore. DRM has stopped to
> select FB because of circular dependency.
> - The CONFIG_FB_MODE_HELPERS are not needed when using DRM
> framebuffer emulation as DRM does.
> - The Acorn fonts are removed, the default framebuffer font
> works fine. I don't know why this was selected in the first
> place or how the Kconfig was altered so it was removed.
>
> Fixes: f611b1e7624c ("drm: Avoid circular dependencies for CONFIG_FB")
> Cc: Kees Cook <keescook@chromium.org>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Ah! Yes, thank you for catching these. :)
Reviewed-by: Kees Cook <keescook@chromium.org>
--
Kees Cook
_______________________________________________
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-14 19:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 8:18 [PATCH] ARM: configs: Update Versatile defconfig Linus Walleij
2021-07-14 8:18 ` Linus Walleij
2021-07-14 19:13 ` Kees Cook [this message]
2021-07-14 19:13 ` Kees Cook
2021-07-16 21:22 ` patchwork-bot+linux-soc
2021-07-16 21:24 ` Arnd Bergmann
2021-07-16 21:24 ` 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=202107141212.757559237F@keescook \
--to=keescook@chromium.org \
--cc=arm@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@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).