All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	PowerPC <linuxppc-dev@lists.ozlabs.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings in powercp build
Date: Thu, 11 May 2023 14:45:44 +1000	[thread overview]
Message-ID: <871qjna32f.fsf@mail.lhotse> (raw)
In-Reply-To: <20230511121635.0a6764a0@canb.auug.org.au>

Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi all,
>
> Today's (and a few before) linux-next build (powerpc pseries_le_defconfig)
> produced these warnings:

Those aren't really warnings, it's just merge_config.sh telling you what
it's doing. The whole point of the generated configs is to override
those symbols.

Looks like there is a way to silence them, by using merge_into_defconfig_override.

cheers

> Building: powerpc pseries_le_defconfig
> Using /home/sfr/next/next/arch/powerpc/configs/ppc64_defconfig as base
> Merging /home/sfr/next/next/arch/powerpc/configs/le.config
> Merging /home/sfr/next/next/arch/powerpc/configs/guest.config
> Value of CONFIG_VIRTIO_BLK is redefined by fragment /home/sfr/next/next/arch/powerpc/configs/guest.config:
> Previous value: CONFIG_VIRTIO_BLK=m
> New value: CONFIG_VIRTIO_BLK=y
>
> Value of CONFIG_SCSI_VIRTIO is redefined by fragment /home/sfr/next/next/arch/powerpc/configs/guest.config:
> Previous value: CONFIG_SCSI_VIRTIO=m
> New value: CONFIG_SCSI_VIRTIO=y
>
> Value of CONFIG_VIRTIO_NET is redefined by fragment /home/sfr/next/next/arch/powerpc/configs/guest.config:
> Previous value: CONFIG_VIRTIO_NET=m
> New value: CONFIG_VIRTIO_NET=y
>
> Value of CONFIG_VIRTIO_CONSOLE is redefined by fragment /home/sfr/next/next/arch/powerpc/configs/guest.config:
> Previous value: CONFIG_VIRTIO_CONSOLE=m
> New value: CONFIG_VIRTIO_CONSOLE=y
>
> Value of CONFIG_VIRTIO_PCI is redefined by fragment /home/sfr/next/next/arch/powerpc/configs/guest.config:
> Previous value: CONFIG_VIRTIO_PCI=m
> New value: CONFIG_VIRTIO_PCI=y
>
> Value of CONFIG_VIRTIO_BALLOON is redefined by fragment /home/sfr/next/next/arch/powerpc/configs/guest.config:
> Previous value: CONFIG_VIRTIO_BALLOON=m
> New value: CONFIG_VIRTIO_BALLOON=y
>
> Value of CONFIG_VHOST_NET is redefined by fragment /home/sfr/next/next/arch/powerpc/configs/guest.config:
> Previous value: CONFIG_VHOST_NET=m
> New value: CONFIG_VHOST_NET=y
>
> Value of CONFIG_IBMVETH is redefined by fragment /home/sfr/next/next/arch/powerpc/configs/guest.config:
> Previous value: CONFIG_IBMVETH=m
> New value: CONFIG_IBMVETH=y
>
> Value of CONFIG_IBMVNIC is redefined by fragment /home/sfr/next/next/arch/powerpc/configs/guest.config:
> Previous value: CONFIG_IBMVNIC=m
> New value: CONFIG_IBMVNIC=y
>
> I am not sure exactly which change(s) introduced these warnings.
>
> -- 
> Cheers,
> Stephen Rothwell

WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	PowerPC <linuxppc-dev@lists.ozlabs.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warnings in powercp build
Date: Thu, 11 May 2023 14:45:44 +1000	[thread overview]
Message-ID: <871qjna32f.fsf@mail.lhotse> (raw)
In-Reply-To: <20230511121635.0a6764a0@canb.auug.org.au>

Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi all,
>
> Today's (and a few before) linux-next build (powerpc pseries_le_defconfig)
> produced these warnings:

Those aren't really warnings, it's just merge_config.sh telling you what
it's doing. The whole point of the generated configs is to override
those symbols.

Looks like there is a way to silence them, by using merge_into_defconfig_override.

cheers

> Building: powerpc pseries_le_defconfig
> Using /home/sfr/next/next/arch/powerpc/configs/ppc64_defconfig as base
> Merging /home/sfr/next/next/arch/powerpc/configs/le.config
> Merging /home/sfr/next/next/arch/powerpc/configs/guest.config
> Value of CONFIG_VIRTIO_BLK is redefined by fragment /home/sfr/next/next/arch/powerpc/configs/guest.config:
> Previous value: CONFIG_VIRTIO_BLK=m
> New value: CONFIG_VIRTIO_BLK=y
>
> Value of CONFIG_SCSI_VIRTIO is redefined by fragment /home/sfr/next/next/arch/powerpc/configs/guest.config:
> Previous value: CONFIG_SCSI_VIRTIO=m
> New value: CONFIG_SCSI_VIRTIO=y
>
> Value of CONFIG_VIRTIO_NET is redefined by fragment /home/sfr/next/next/arch/powerpc/configs/guest.config:
> Previous value: CONFIG_VIRTIO_NET=m
> New value: CONFIG_VIRTIO_NET=y
>
> Value of CONFIG_VIRTIO_CONSOLE is redefined by fragment /home/sfr/next/next/arch/powerpc/configs/guest.config:
> Previous value: CONFIG_VIRTIO_CONSOLE=m
> New value: CONFIG_VIRTIO_CONSOLE=y
>
> Value of CONFIG_VIRTIO_PCI is redefined by fragment /home/sfr/next/next/arch/powerpc/configs/guest.config:
> Previous value: CONFIG_VIRTIO_PCI=m
> New value: CONFIG_VIRTIO_PCI=y
>
> Value of CONFIG_VIRTIO_BALLOON is redefined by fragment /home/sfr/next/next/arch/powerpc/configs/guest.config:
> Previous value: CONFIG_VIRTIO_BALLOON=m
> New value: CONFIG_VIRTIO_BALLOON=y
>
> Value of CONFIG_VHOST_NET is redefined by fragment /home/sfr/next/next/arch/powerpc/configs/guest.config:
> Previous value: CONFIG_VHOST_NET=m
> New value: CONFIG_VHOST_NET=y
>
> Value of CONFIG_IBMVETH is redefined by fragment /home/sfr/next/next/arch/powerpc/configs/guest.config:
> Previous value: CONFIG_IBMVETH=m
> New value: CONFIG_IBMVETH=y
>
> Value of CONFIG_IBMVNIC is redefined by fragment /home/sfr/next/next/arch/powerpc/configs/guest.config:
> Previous value: CONFIG_IBMVNIC=m
> New value: CONFIG_IBMVNIC=y
>
> I am not sure exactly which change(s) introduced these warnings.
>
> -- 
> Cheers,
> Stephen Rothwell

  reply	other threads:[~2023-05-11  4:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11  2:16 linux-next: build warnings in powercp build Stephen Rothwell
2023-05-11  2:16 ` Stephen Rothwell
2023-05-11  4:45 ` Michael Ellerman [this message]
2023-05-11  4:45   ` Michael Ellerman

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=871qjna32f.fsf@mail.lhotse \
    --to=mpe@ellerman.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.