From: Stephen Rothwell <sfr@canb•auug.org.au>
To: David Howells <dhowells@redhat•com>,
Masahiro Yamada <masahiroy@kernel•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 after merge of the notifications (was keys) tree
Date: Tue, 12 May 2020 18:54:03 +1000 [thread overview]
Message-ID: <20200512185403.15297945@canb.auug.org.au> (raw)
In-Reply-To: <20200504134750.2278a82d@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
Hi all,
On Mon, 4 May 2020 13:47:50 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Hi all,
>
> After merging the keys tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
>
> scripts/Makefile.lib:8: 'always' is deprecated. Please use 'always-y' instead
> scripts/Makefile.lib:12: 'hostprogs-y' and 'hostprogs-m' are deprecated. Please use 'hostprogs' instead
>
> Introduced by commit
>
> 631ec151fd96 ("Add sample notification program")
>
> interacting with commit
>
> ee066c3ddf7b ("kbuild: warn if always, hostprogs-y, or hostprogs-m is used")
>
> from the kbuild tree.
This is now Introduced by commit
b8c9527a31b0 ("Add sample notification program")
from the notifications tree interacting with commit
a2db26b0ba3b ("kbuild: warn if always, hostprogs-y, or hostprogs-m is used")
from the kbuild tree.
It only produces these warnings now:
scripts/Makefile.lib:8: 'always' is deprecated. Please use 'always-y' instead
scripts/Makefile.lib:12: 'hostprogs-y' is deprecated. Please use 'hostprogs' instead
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-05-12 8:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 3:47 linux-next: build warnings after merge of the keys tree Stephen Rothwell
2020-05-12 8:54 ` Stephen Rothwell [this message]
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=20200512185403.15297945@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dhowells@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=masahiroy@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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