linux-kernel - Re: linux-next: Tree for Jan 7

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+icZUWr8gv3vZWdgBT7ovVxHt-kGimgzLhc4=CZLVYoAwJc3g@mail.gmail.com>
Date:	Wed, 7 Jan 2015 08:34:30 +0100
From:	Sedat Dilek <sedat.dilek@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next <linux-next@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for Jan 7

On Wed, Jan 7, 2015 at 5:16 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi all,
>
> Changes since 20150106:
>
> *crickets*
>
> Non-merge commits (relative to Linus' tree): 1350
>  1543 files changed, 41856 insertions(+), 24250 deletions(-)
>

Happy new year,

this release is a very special for me.
I had to apply zero null nada patches of mine or others :-).

The calm days between Xmas and new year, I started again to build and
test Linux-next (aka v3.20) kernels .

This was primarily to play with loop-mq from block-next tree.
As a sidenote I reported some bugs in fio, now we have v2.2.4.

En plus, I refreshed my build-script for -next (see attached file).
And I am really happy to see my builddeb patches in kbuild-next.

Thanks to all involved people.

Regards,
- Sedat -

> ----------------------------------------------------------------------------
>
> 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 234 trees (counting Linus' and 32 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@...b.auug.org.au
>

Download attachment "build_linux-next.sh" of type "application/x-sh" (5152 bytes)