From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Nick Krause <xerofoify@gmail•com>
Cc: "linux-next@vger•kernel.org" <linux-next@vger•kernel.org>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for Jul 16
Date: Thu, 17 Jul 2014 11:47:18 +1000 [thread overview]
Message-ID: <20140717114718.3895d851@canb.auug.org.au> (raw)
In-Reply-To: <CAPDOMVh5_JXKwPQ9EwtXHLYnqNRhEMedF5F5K7H+PEqMuCZa8Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
Hi Nick,
On Wed, 16 Jul 2014 21:16:16 -0400 Nick Krause <xerofoify@gmail•com> wrote:
>
> > On Wed, 16 Jul 2014 20:45:25 -0400 Nick Krause <xerofoify@gmail•com> wrote:
> >>
> >> On Wed, Jul 16, 2014 at 4:45 AM, Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> >> >
> >> > Status of my local build tests will be at
> >> > http://kisskb.ellerman.id.au/linux-next .
> >
> >> I am trying to get the maintainers to clean up still failing builds.
> >> When you get time I wondering
> >> if you can send me a list of still failing builds and warnings of
> >> interest in the kernel that is'
> >> up to date for me to help clean up these outstanding issues with the
> >> maintainers support as needed.
> >
> > See above ...
>
> There seems to be a few that are still succeeding for me that aren't for.
> Would you mind testing some of them again to see if they are succeeding
> with a gcc compiler that is newer then version 4.7.
Please tell us exactly what you are testing: what kernel version, what
compiler/binutils version. The kernel is meant to be able to be built
with gcc 4.7 (and some earlier) - barring compiler bugs, of course.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-07-17 1:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 8:45 linux-next: Tree for Jul 16 Stephen Rothwell
2014-07-17 0:45 ` Nick Krause
2014-07-17 0:51 ` Stephen Rothwell
2014-07-17 1:16 ` Nick Krause
2014-07-17 1:47 ` Stephen Rothwell [this message]
2014-07-17 2:01 ` Nick Krause
2014-07-17 3:14 ` Stephen Rothwell
2014-07-17 3:39 ` Nick Krause
-- strict thread matches above, loose matches on Subject: below --
2025-07-16 11:25 Stephen Rothwell
2024-07-16 6:59 Stephen Rothwell
2021-07-16 5:48 Stephen Rothwell
2020-07-16 8:53 Stephen Rothwell
2019-07-16 5:47 Stephen Rothwell
2018-07-16 7:56 Stephen Rothwell
2015-07-16 6:28 Stephen Rothwell
2013-07-16 5:56 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=20140717114718.3895d851@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=xerofoify@gmail$(echo .)com \
/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