From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Nick Krause <xerofoify@gmail•com>
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: Fri, 18 Jul 2014 09:03:25 +1000 [thread overview]
Message-ID: <20140718090325.32eb36bb@canb.auug.org.au> (raw)
In-Reply-To: <CAPDOMViJfR2qqNRkx_mKpQ0FWd76YN77ev3M=0boZFW6NvS3Pg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-07-17 23:03 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 [this message]
2014-07-18 2:58 ` Nick Krause
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=20140718090325.32eb36bb@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