From: Nick Krause <xerofoify@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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: Wed, 16 Jul 2014 23:39:30 -0400 [thread overview]
Message-ID: <CAPDOMVjsmEVjyAaOgyLA3ybe+tCXwjrdJk3w=abEV1rNQ5zURg@mail.gmail.com> (raw)
In-Reply-To: <20140717131457.15f3fb4d@canb.auug.org.au>
On Wed, Jul 16, 2014 at 11:14 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Nick,
>
> On Wed, 16 Jul 2014 22:01:35 -0400 Nick Krause <xerofoify@gmail.com> wrote:
>>
>> Absolutely , I am using the latest kernel rc from git. I am using gcc
>> 4.8.3 and binutils 2.83.91.
>
> Then that has nothing to do with me ... I am the linux-next
> maintainer. I just happen to use the same build test system as is also
> used to test Linus' tree (kisskb). I hope you are looking at the right
> result pages for what you are testing. The URL I gave you was for the
> linux-next builds, not Linus' tree.
>
>> In addition I am using the default configurations as you are in less
>> I am doing it differently.
>> By the way xtensa-defconfig seems to fail because of binutils as I
>> discussed this with
>> the maintainers and they seemed to have tested it with a newer upstream binutils
>> then I am using and it succeeded it the linking failures I am seeing with it.
>
> Maybe we need per architecture minimum tools versions (instead of
> current global one).
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
That seems like a good idea. I am also curious if when there is a
build failure in
the mainline kernel if we can mail the logs to the maintainers of that
arch as if
we do it seems to get resolved much faster, usually in a day or two,
Cheers Nick
next prev parent reply other threads:[~2014-07-17 3:39 UTC|newest]
Thread overview: 14+ 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
2014-07-17 2:01 ` Nick Krause
2014-07-17 3:14 ` Stephen Rothwell
2014-07-17 3:39 ` Nick Krause [this message]
-- strict thread matches above, loose matches on Subject: below --
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='CAPDOMVjsmEVjyAaOgyLA3ybe+tCXwjrdJk3w=abEV1rNQ5zURg@mail.gmail.com' \
--to=xerofoify@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 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).