From: Nick Krause <xerofoify@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: Build allyesconfig for PowerPc tested
Date: Thu, 17 Jul 2014 22:58:59 -0400 [thread overview]
Message-ID: <CAPDOMVjOVW3y9cc-6wnh0wtoX9F8AMCNZ4WDV5QJFn4riQ2WXg@mail.gmail.com> (raw)
In-Reply-To: <20140718090325.32eb36bb@canb.auug.org.au>
On Thu, Jul 17, 2014 at 7:03 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Nick,
>
> On Thu, 17 Jul 2014 14:49:29 -0400 Nick Krause <xerofoify@gmail.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@canb.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
prev parent reply other threads:[~2014-07-18 2:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 18:49 Build allyesconfig for PowerPc tested Nick Krause
2014-07-17 23:03 ` Stephen Rothwell
2014-07-18 2:58 ` Nick Krause [this message]
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=CAPDOMVjOVW3y9cc-6wnh0wtoX9F8AMCNZ4WDV5QJFn4riQ2WXg@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).