From: Kees Cook <keescook@google.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Emese Revfy <re.emese@gmail.com>
Subject: Re: linux-next: build warnings after merge of the kspp tree
Date: Wed, 22 Jun 2016 10:10:13 -0700 [thread overview]
Message-ID: <CAGXu5jJe5G5N9BJeB3dr0hKF+A0NOLT5OjQDOpMwko4fHr4OwA@mail.gmail.com> (raw)
In-Reply-To: <20160622151442.5684f922@canb.auug.org.au>
On Tue, Jun 21, 2016 at 10:14 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Kees,
>
> After merging the kspp tree, today's linux-next build (i386 defconfig)
> produced these warning:
>
> x86_64-linux-gcc: warning: '-mcpu=' is deprecated; use '-mtune=' or '-march=' instead
>
> (over 2000 of these)
>
> Introduced (maybe) by commit
>
> e2135c84d5d2 ("kbuild: no gcc-plugins during cc-option tests")
I will investigate.
-Kees
--
Kees Cook
Chrome OS & Brillo Security
next prev parent reply other threads:[~2016-06-22 17:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 5:14 linux-next: build warnings after merge of the kspp tree Stephen Rothwell
2016-06-22 17:10 ` Kees Cook [this message]
2016-06-22 17:39 ` Kees Cook
2021-08-26 8:00 Stephen Rothwell
2021-08-27 3:29 ` Kees Cook
2024-02-05 5:14 Stephen Rothwell
2024-02-05 12:43 ` Kees Cook
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=CAGXu5jJe5G5N9BJeB3dr0hKF+A0NOLT5OjQDOpMwko4fHr4OwA@mail.gmail.com \
--to=keescook@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=re.emese@gmail.com \
--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.