public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 17:57:54 +0200	[thread overview]
Message-ID: <20201011155754.GC15925@zn.tnic> (raw)
In-Reply-To: <107a6fb0-a667-2f30-d1f4-640e3fee193a@collabora.com>

On Sun, Oct 11, 2020 at 05:40:27PM +0200, Enric Balletbo i Serra wrote:
> How do you quantify those things are NOT common enough? Do you have a number?

I don't want to change the defconfig - you do. So quantifying is in your
court - not mine.

> I don't have a number, the only I can tell is that both symbols enable support
> for I2C, SPI an HS-UART. The AMD one, is found on AMD Carrizo and later
> chipsets, the Intel one, is found on Intel Skylake and later. I.e Lots of
> laptops need these to have support for the touchpad.

That sounds like a step in the right direction.

> KernelCI is focused on upstream kernel development. KernelCI builds lots of
> different versions of the kernel, including stable kernels, and maintainers
> trees. It does tests on real hardware, so having a config supporting as much as
> possible the x86 hardware that we have in the KernelCI labs will help us to
> increase the test coverage and catch more issues.

So those issues - where do you guys report them? Because I've never seen
one reported by kernelCI, AFAIR. I see 0day bot and syzbot doing such
reports on a regular basis but none from kernelCI AFAIK. Do you send
your bug reports to lkml and Cc the relevant parties?

> Yes, it can. As I said, is a matter of maintenance, if we do this we
> will have a different workflow for x86 hardware.

Lemme get this straight - your workflow would do:

$ make defconfig

and now here you'd have to add a single command:

$ .scripts/kconfig/merge_config.sh -m .config .kernelci.config.snippet

in order to get the symbols you want, enabled.

I've shown this one because this is how those other configs like
kvm_guest.config and xen.config work - they're config snippets and they
get merged with a preexisting config, see scripts/kconfig/Makefile.

Now, is that additional single command worth "hours of maintenance time"
or is it something you can do easily? As in:

	if (x86)
		<command>

?

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2020-10-11 15:58 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
2020-10-11 15:40         ` Enric Balletbo i Serra
2020-10-11 15:57           ` Borislav Petkov [this message]
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=20201011155754.GC15925@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