From: Arnd Bergmann <arnd@kernel.org>
To: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: Kees Cook <keescook@chromium.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Randy Dunlap <rdunlap@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
John Youn <John.Youn@synopsys.com>,
Bing Yuan <Bing.Yuan@synopsys.com>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Kconfig CONFIG_FB dependency regression
Date: Wed, 9 Feb 2022 08:06:38 +0100 [thread overview]
Message-ID: <CAK8P3a3bJcMKW5QJqoUT8jDe+cbK0A-zSbNZhveX0WwC=ZEUqw@mail.gmail.com> (raw)
In-Reply-To: <1aef3a8f-f93e-2824-6b6e-8df8a1460f15@synopsys.com>
On Tue, Feb 8, 2022 at 11:42 PM Thinh Nguyen <Thinh.Nguyen@synopsys.com> wrote:
> Randy Dunlap wrote:
> > On 2/8/22 12:10, Thinh Nguyen wrote:
> >> Randy Dunlap wrote:
> >>> On 2/3/22 19:21, Thinh Nguyen wrote:
> Ah.. It's because I don't use old.config as the base config. I use
> x86_64_defconfig as the base plus some additional configs I need, and it
> has CONFIG_FB_EFI set by default.
Does it hang if you just disable CONFIG_FB_EFI on an otherwise working
kernel? This is supposed to only disable the framebuffer, but it could be
the actual cause if something else depends on its presence.
Arnd
next prev parent reply other threads:[~2022-02-09 7:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 23:01 Kconfig CONFIG_FB dependency regression Thinh Nguyen
2022-02-01 23:06 ` Randy Dunlap
2022-02-01 23:59 ` Fabio Estevam
2022-02-02 0:14 ` Thinh Nguyen
2022-02-02 7:46 ` Arnd Bergmann
2022-02-02 23:55 ` Thinh Nguyen
2022-02-03 3:15 ` Randy Dunlap
2022-02-03 4:23 ` Thinh Nguyen
2022-02-03 7:18 ` Arnd Bergmann
2022-02-04 3:21 ` Thinh Nguyen
2022-02-04 4:02 ` Randy Dunlap
2022-02-08 20:10 ` Thinh Nguyen
2022-02-08 20:45 ` Randy Dunlap
2022-02-08 22:42 ` Thinh Nguyen
2022-02-09 7:06 ` Arnd Bergmann [this message]
2022-02-15 2:52 ` Thinh Nguyen
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='CAK8P3a3bJcMKW5QJqoUT8jDe+cbK0A-zSbNZhveX0WwC=ZEUqw@mail.gmail.com' \
--to=arnd@kernel.org \
--cc=Bing.Yuan@synopsys.com \
--cc=John.Youn@synopsys.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=rdunlap@infradead.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).