linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next <linux-next@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Jan 7
Date: Wed, 7 Jan 2015 08:34:30 +0100	[thread overview]
Message-ID: <CA+icZUWr8gv3vZWdgBT7ovVxHt-kGimgzLhc4=CZLVYoAwJc3g@mail.gmail.com> (raw)
In-Reply-To: <20150107151618.7cb9d574@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 2471 bytes --]

On Wed, Jan 7, 2015 at 5:16 AM, Stephen Rothwell <sfr@canb.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@canb.auug.org.au
>

[-- Attachment #2: build_linux-next.sh --]
[-- Type: application/x-sh, Size: 5152 bytes --]

  reply	other threads:[~2015-01-07  7:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-07  4:16 linux-next: Tree for Jan 7 Stephen Rothwell
2015-01-07  7:34 ` Sedat Dilek [this message]
2015-01-07 14:26 ` Guenter Roeck
2015-01-07 16:33   ` Paul E. McKenney
2015-01-07 17:30     ` Guenter Roeck
2015-01-07 18:09       ` Paul E. McKenney
2015-01-07 19:18         ` Guenter Roeck
2015-01-07 20:00           ` Christian Borntraeger
2015-01-07 20:33             ` Guenter Roeck
2015-01-07 21:45 ` linux-next: Tree for Jan 7 (microblaze qemu problems) Guenter Roeck
2015-01-08  5:58   ` Guenter Roeck
2015-01-08  6:56     ` Michal Simek
  -- strict thread matches above, loose matches on Subject: below --
2022-01-07 15:43 linux-next: Tree for Jan 7 Stephen Rothwell
2021-01-07  3:01 Stephen Rothwell
2020-01-07  6:03 Stephen Rothwell
2019-01-07  4:06 Stephen Rothwell
2019-01-07  7:35 ` Geert Uytterhoeven
2019-01-07 11:49   ` Michael Ellerman
2019-01-07 13:56     ` Michael Ellerman
2019-01-08  2:28       ` Michael Ellerman
2016-01-07 10:21 Stephen Rothwell
2014-01-07  6:38 Stephen Rothwell
2013-01-07  3:26 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='CA+icZUWr8gv3vZWdgBT7ovVxHt-kGimgzLhc4=CZLVYoAwJc3g@mail.gmail.com' \
    --to=sedat.dilek@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).