All of lore.kernel.org
 help / color / mirror / Atom feed
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 11
Date: Sun, 13 Jul 2014 00:08:48 -0400	[thread overview]
Message-ID: <CAPDOMVi1fb5Moj8QYLW4bk07KysBoObtW8Y+vxssuz9LR3Ef+Q@mail.gmail.com> (raw)
In-Reply-To: <CAPDOMVgi8Cw8z_i7bTEXQSRWbOiu7kQSpAnnDkyWCkr=yf7xsQ@mail.gmail.com>

On Sat, Jul 12, 2014 at 6:26 PM, Nick Krause <xerofoify@gmail.com> wrote:
> On Fri, Jul 11, 2014 at 3:18 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> Hi all,
>>
>> Changes since 20140710:
>>
>> My fixes tree contains:
>>         powerpc: Disable RELOCATABLE for COMPILE_TEST with PPC64
>>
>> The tty.current tree gained a build failure so I used the version from
>> next-20140710.
>>
>> The irqchip tree gained a conflict against the arm64 tree.
>>
>> The staging tree lost its build failure and gained a conflict against
>> the tty tree.
>>
>> Non-merge commits (relative to Linus' tree): 5114
>>  4474 files changed, 191199 insertions(+), 226003 deletions(-)
>>
>> ----------------------------------------------------------------------------
>>
>> I have created today's linux-next tree at
>> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>> (patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
>> are tracking the linux-next tree using git, you should not use "git pull"
>> to do so as that will try to merge the new linux-next release with the
>> old one.  You should use "git fetch" and checkout or reset to the new
>> master.
>>
>> You can see which trees have been included by looking in the Next/Trees
>> file in the source.  There are also quilt-import.log and merge.log files
>> in the Next directory.  Between each merge, the tree was built with
>> a ppc64_defconfig for powerpc and an allmodconfig for x86_64 and a
>> multi_v7_defconfig for arm. After the final fixups (if any), it is also
>> built with powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig and
>> allyesconfig (this fails its final link) and i386, sparc, sparc64 and arm
>> defconfig.
>>
>> Below is a summary of the state of the merge.
>>
>> I am currently merging 222 trees (counting Linus' and 30 trees of patches
>> pending for Linus' tree).
>>
>> Stats about the size of the tree over time can be seen at
>> http://neuling.org/linux-next-size.html .
>>
>> Status of my local build tests will be at
>> http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
>> advice about cross compilers/configs that work, we are always open to add
>> more builds.
>>
>> Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
>> Gortmaker for triage and bug fixes.
>>
>> --
>> Cheers,
>> Stephen Rothwell                    sfr@canb.auug.org.au
>>

> I am been trying your tests for a while. Seems most of your failing
> tests work for me.
> Can you test a newer compiler in the 4.8 release series for gcc to see
> if this fixes your
> issues.
> Cheers Nick
I am also attaching logs of build I have that are succeeding to help
you.Furthermore I run the builds in two steps listed below using
compilers for
Ubuntu 14.04 and Fedora 20 turned into dpkgs to work with Debian
distros.Below are the steps.
1. make ARCH=x y_defconfig
2.ARCH= x CROSS_COMPILE=z make -j 8 2> error_file
x = cpu architecture  I am building
y=configuration I am building
z= gcc I am builds this architecture
error_file = file I am tracing errors and warnings to send if build
fails to maintainers of that architecture
If you have any other questions please ask me.
Cheers Nick

  reply	other threads:[~2014-07-13  4:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-11  7:18 linux-next: Tree for Jul 11 Stephen Rothwell
2014-07-11 18:31 ` linux-next: Tree for Jul 11 (media/pci/ttpci/av7110) Randy Dunlap
2014-07-12 22:26 ` linux-next: Tree for Jul 11 Nick Krause
2014-07-13  4:08   ` Nick Krause [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-11  2:15 Stephen Rothwell
2022-07-11 11:12 Stephen Rothwell
2019-07-11  9:47 Stephen Rothwell
2018-07-11  6:40 Stephen Rothwell
2017-07-11  4:57 Stephen Rothwell
2016-07-11  8:55 Stephen Rothwell
2013-07-11  4:17 Stephen Rothwell
2013-07-11  4:17 ` 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=CAPDOMVi1fb5Moj8QYLW4bk07KysBoObtW8Y+vxssuz9LR3Ef+Q@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.