On Tue, 11 Jan 2022 at 17:49, Robert Berger
wrote:
> Is this only one defconfig and nothing else or a defconfig plus fragments?
>
> I build with an upstream 5.15.13 kernel with multi_v7_defconfig and it
> does not spit out any warnings. Not even after adding some of my own
> fragments.
I've been
Hi,
On 11/01/2022 15:57, Ross Burton wrote:
On Tue, 11 Jan 2022 at 13:55, Ross Burton via lists.openembedded.org
wrote:
The standard linux-yocto builds using config fragments, but it's a
supported option to use the standard defconfig.
However, our enhanced config checking means that defconfig
On Tue, Jan 11, 2022 at 8:57 AM Ross Burton wrote:
>
> On Tue, 11 Jan 2022 at 13:55, Ross Burton via lists.openembedded.org
> wrote:
> > The standard linux-yocto builds using config fragments, but it's a
> > supported option to use the standard defconfig.
> >
> > However, our enhanced config chec
On Tue, 11 Jan 2022 at 13:55, Ross Burton via lists.openembedded.org
wrote:
> The standard linux-yocto builds using config fragments, but it's a
> supported option to use the standard defconfig.
>
> However, our enhanced config checking means that defconfig will often
> cause configure warnings.
The standard linux-yocto builds using config fragments, but it's a
supported option to use the standard defconfig.
However, our enhanced config checking means that defconfig will often
cause configure warnings. Add a test suite that exercises a defconfig
build is successful without any warnings.
