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 14
Date: Mon, 14 Jul 2014 13:50:40 -0400	[thread overview]
Message-ID: <CAPDOMViMv48o9_3tRp+AJLGy7XCM8ggPR6x9KXSfah+Xyvrjxg@mail.gmail.com> (raw)
In-Reply-To: <20140714171755.22901059@canb.auug.org.au>

On Mon, Jul 14, 2014 at 3:17 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> Changes since 20140711:
>
> My fixes tree is empty again.
>
> The tty.current tree lost its build failure.
>
> The mvebu tree gained a conflict against Linus' tree.
>
> The akpm tree lost a few patches that turned up elsewhere.
>
> Non-merge commits (relative to Linus' tree): 5571
>  5123 files changed, 207687 insertions(+), 256904 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 running your failing tests and most of them seem to succeed for me.
I also sent you a log of these succeeding builds.
Cheers Nick

  reply	other threads:[~2014-07-14 17:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14  7:17 linux-next: Tree for Jul 14 Stephen Rothwell
2014-07-14 17:50 ` Nick Krause [this message]
2015-07-14  5:41 Stephen Rothwell
2016-07-14  6:18 Stephen Rothwell
2017-07-14  3:58 Stephen Rothwell
2020-07-14 10:03 Stephen Rothwell
2021-07-14  3:25 Stephen Rothwell
2022-07-14  8:55 Stephen Rothwell
2022-07-14 11:07 ` Sudip Mukherjee (Codethink)
2022-07-14 16:05   ` Nathan Chancellor
2022-07-14 16:21     ` Sudip Mukherjee
2022-07-14 16:29       ` Nathan Chancellor
2022-07-14 16:55         ` Sudip Mukherjee
2022-07-14 18:26         ` Sudip Mukherjee
2022-07-14 21:24           ` Nathan Chancellor
2022-07-15 22:06             ` Sudip Mukherjee
2022-07-17 22:05             ` Sudip Mukherjee
2022-07-14 18:51       ` Nick Desaulniers
2022-07-15 19:31         ` Sudip Mukherjee
2023-07-14  4:15 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=CAPDOMViMv48o9_3tRp+AJLGy7XCM8ggPR6x9KXSfah+Xyvrjxg@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.