From: Borislav Petkov <bp@alien8.de>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
"Collabora Kernel ML" <kernel@collabora.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Diego Elio Pettenò" <flameeyes@flameeyes.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"Nathan Chancellor" <natechancellor@gmail.com>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Willy Tarreau" <w@1wt.eu>
Subject: Re: [PATCH] x86/x86_64_defconfig: Enable the serial console
Date: Thu, 8 Oct 2020 18:40:44 +0200 [thread overview]
Message-ID: <20201008164044.GE5505@zn.tnic> (raw)
In-Reply-To: <20201008162206.862203-1-enric.balletbo@collabora.com>
On Thu, Oct 08, 2020 at 06:22:06PM +0200, Enric Balletbo i Serra wrote:
> As part of KernelCI, we added a bunch of different x86 based Chromebooks
> to do test booting and runtime testing. It will be useful have serial
> support for these platforms in the default defconfig, as this, is the
> defconfig used by default for the different maintainer's tree.
>
> SERIAL_8250_DW is the actual support for the console, but to have
> support we need to enable X86_AMD_PLATFORM_DEVICE for specific AMD
> boards and MFD_INTEL for specific Intel boards.
>
> While here, also enable USB_RTL8152 config which enables a common
> USB-Ethernet adapter used very commonly in the KernelCI labs.
To me defconfig sounds like the config which contains items which are
needed on the majority of x86 hardware out there.
Are those which you enable that common and if not, why can't your build
supply a custom .config instead?
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-10-08 16:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 16:22 [PATCH] x86/x86_64_defconfig: Enable the serial console Enric Balletbo i Serra
2020-10-08 16:40 ` Borislav Petkov [this message]
2020-10-08 18:31 ` Randy Dunlap
2020-10-11 11:43 ` Enric Balletbo i Serra
2020-10-11 12:20 ` Borislav Petkov
2020-10-11 15:40 ` Enric Balletbo i Serra
2020-10-11 15:57 ` Borislav Petkov
2020-10-11 17:05 ` Enric Balletbo i Serra
2020-10-11 19:06 ` Borislav Petkov
2020-10-12 3:58 ` Willy Tarreau
2020-10-12 10:22 ` Guillaume Tucker
2020-10-12 14:32 ` Borislav Petkov
2020-10-12 14:40 ` Willy Tarreau
2020-10-12 15:10 ` Guillaume Tucker
2020-10-12 16:43 ` Borislav Petkov
2020-10-12 17:52 ` Nick Desaulniers
2020-10-12 16:39 ` Borislav Petkov
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=20201008164044.GE5505@zn.tnic \
--to=bp@alien8.de \
--cc=enric.balletbo@collabora.com \
--cc=flameeyes@flameeyes.com \
--cc=hpa@zytor.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mingo@redhat.com \
--cc=natechancellor@gmail.com \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--cc=w@1wt.eu \
--cc=x86@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