From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Kees Cook <keescook@chromium.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Bart Van Assche <bart.vanassche@wdc.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: Tree for Mar 13
Date: Wed, 14 Mar 2018 07:08:46 +1100 [thread overview]
Message-ID: <20180314070707.2d3c1807@canb.auug.org.au> (raw)
In-Reply-To: <CAMM=eLdZ6adSV6Q0JLkRi9k=7g5o4SEAyGfOm0P_nqw71Jbing@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 717 bytes --]
Hi Mike,
On Tue, 13 Mar 2018 11:57:40 -0400 Mike Snitzer <snitzer@redhat.com> wrote:
>
> I had to revert the following commits to get this kernel to build
> (otherwise I got macro expansion errors, using RHEL7
> gcc-4.8.5-28.el7.x86_64):
Yeah, I reported that earlier (216 of my 244 builds failed - gcc 4.6.3)
> beb7eb2 kernelh-skip-single-eval-logic-on-literals-in-min-max-v3
> 19ff7e5 kernelh-skip-single-eval-logic-on-literals-in-min-max-v2
> c7c133f kernel.h: skip single-eval logic on literals in min()/max()
>
> (it wasn't until I reverted commit c7c133f that the kernel build worked)
I will revert those from linux-next today unless someone sends a fix.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-03-13 20:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 7:33 linux-next: Tree for Mar 13 Stephen Rothwell
2018-03-13 15:57 ` Mike Snitzer
2018-03-13 17:30 ` Randy Dunlap
2018-03-13 19:52 ` Kees Cook
2018-03-13 20:08 ` Stephen Rothwell [this message]
[not found] ` <20180313175205.GA15734@light.dominikbrodowski.net>
2018-03-13 20:48 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2024-03-13 4:13 Stephen Rothwell
2020-03-13 11:03 Stephen Rothwell
2015-03-13 6:36 Stephen Rothwell
2014-03-13 18:53 Mark Brown
2013-03-13 5:48 Stephen Rothwell
2012-03-13 9:41 Stephen Rothwell
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=20180314070707.2d3c1807@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=bart.vanassche@wdc.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=snitzer@redhat.com \
/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).