From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: build warnings from Linus' tree
Date: Fri, 30 Aug 2019 07:59:02 +1000 [thread overview]
Message-ID: <20190830075902.255b9c70@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 680 bytes --]
Hi all,
With just Linus' tree, today's linux-next build (ppc64le perf) produced
these warnings:
util/parse-events.y:1.1-12: warning: deprecated directive, use '%define api.pure' [-Wdeprecated]
1 | %pure-parser
| ^~~~~~~~~~~~
util/parse-events.y: warning: fix-its can be applied. Rerun with option '--update'. [-Wother]
util/expr.y:13.1-12: warning: deprecated directive, use '%define api.pure' [-Wdeprecated]
13 | %pure-parser
| ^~~~~~~~~~~~
util/expr.y: warning: fix-its can be applied. Rerun with option '--update'. [-Wother]
I assume this is because I have upgraded bison to version 3.4.1 (from
3.3.2).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-08-29 21:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 21:59 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-08-19 22:13 linux-next: build warnings from Linus' tree Stephen Rothwell
2018-08-19 22:16 ` Stephen Rothwell
2018-08-19 22:40 ` Stephen Rothwell
2018-08-19 23:21 ` Linus Torvalds
2018-08-20 1:33 ` Adam Borowski
2018-08-20 2:53 ` Theodore Y. Ts'o
2018-08-20 0:02 ` Theodore Y. Ts'o
2018-08-20 17:47 ` Miguel Ojeda
2018-06-11 22:14 Stephen Rothwell
2018-11-14 4:54 ` Joel Stanley
2018-11-14 10:20 ` Michael Ellerman
2018-11-18 11:22 ` Alan Modra
2018-12-03 23:24 ` Joel Stanley
2010-10-28 0:27 Stephen Rothwell
2010-10-28 3:04 ` Mark Brown
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=20190830075902.255b9c70@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).