From: Borislav Petkov <bp@alien8.de>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: "Randy Dunlap" <rdunlap@infradead.org>,
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>,
"Willy Tarreau" <w@1wt.eu>
Subject: Re: [PATCH] x86/x86_64_defconfig: Enable the serial console
Date: Sun, 11 Oct 2020 14:20:20 +0200 [thread overview]
Message-ID: <20201011122020.GA15925@zn.tnic> (raw)
In-Reply-To: <2538da14-0f4b-5d4a-c7bf-6fdb46ba2796@collabora.com>
On Sun, Oct 11, 2020 at 01:43:44PM +0200, Enric Balletbo i Serra wrote:
> We're also probably lacking a definition of what normal users mean, because I
> don't think normal users build their own kernel.
You'd be surprised.
> I think that at least X86_AMD_PLATFORM_DEVICE and MFD_INTEL_LPSS_PCI
> could be common enough to match within the category of needed to run
> in normal (or common) user mode(s). I can send a patch with only these
> two options.
How do you quantify those things are common enough?
> But, yes, the main purpose after this patch is the serial console for CI. I saw
> that there are already some configs with a specific purpose (tiny.config and
> xen.config). So, I am wondering if would be acceptable support another specific
> config for CI (i.e kernelci.config). Will it be acceptable?
Why does this config have to be upstream? Can't your build process
supply it? Also, can your config be of any use outside of kernel CI?
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-10-11 12:20 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
2020-10-08 18:31 ` Randy Dunlap
2020-10-11 11:43 ` Enric Balletbo i Serra
2020-10-11 12:20 ` Borislav Petkov [this message]
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=20201011122020.GA15925@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