[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAPDOMVjOVW3y9cc-6wnh0wtoX9F8AMCNZ4WDV5QJFn4riQ2WXg@mail.gmail.com>
Date: Thu, 17 Jul 2014 22:58:59 -0400
From: Nick Krause <xerofoify@...il.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>
Subject: Re: Build allyesconfig for PowerPc tested
On Thu, Jul 17, 2014 at 7:03 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi Nick,
>
> On Thu, 17 Jul 2014 14:49:29 -0400 Nick Krause <xerofoify@...il.com> wrote:
>>
>> For a while allyesconfig for powerpc seemed to fail building I ran the
>> test today to check if
>> it builds. It seems to build for me but with warnings. Furthermore
>> there seem to be a few
>> warnings that need clean up. I can either send another email to the
>> maintainers of the powerpc
>> architecture branch or you can with my logs as I am attaching them here,
>
> Powerpc allyesconfig will not build completely, this has been known for
> a long time. Even your log shows it failing, so I do not understand
> what you are saying. (BTW, that is not the normal way for the build to
> fail, it will always fail when trying to link vmlinux. Maybe you are
> missing some tool to build the kernel signing keys?)
>
> You should report warnings/failures in subsystems to the appropriate
> subsyetem maintainer, just because you get these for a particular
> architecture does not mean that they are the responsibility of that
> architecture maintainer.
>
> --
> Cheers,
> Stephen Rothwell sfr@...b.auug.org.au
That's fine I will send this to the maintainer of the powerpc architecture .
I would like to see this get mixed soon.
Cheers Nick
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists