Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1283455 > unrolled thread

linux-next: Tree for 3rd December

Back to article view | Back to linux.kernel

Contents

  linux-next: Tree for 3rd December Mark Brown <broonie@kernel.org> - 2015-12-04 00:40 +0100
    Re: linux-next: Tree for 3rd December Stephen Rothwell <sfr@canb.auug.org.au> - 2015-12-06 23:50 +0100

#1283455 — linux-next: Tree for 3rd December

[Multipart message — attachments visible in raw view] — view raw

Hi all,

Changes since 20151202:

Both of Andrew's trees are included.

The block and gpio trees still have their build failures so I used the
versions from next-20151127.

There were several new conflicts between the drm-intel-fixes and
drm-next trees.

It is very unlikely that there will be a build tomorrow, Stephen will be
back and -next will be back to normal on Monday.

Non-merge commits (relative to Linus' tree): 3709
 5435 files changed, 721155 insertions(+), 627700 deletions(-)

I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
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 defconfig for arm64 and an allmodconfig for x86_64, a
multi_v7_defconfig for arm and a native build of tools/perf.

[toc] | [next] | [standalone]

#1284939

Hi Mark,

On Thu, 3 Dec 2015 23:31:43 +0000 Mark Brown <broonie@kernel.org> wrote:
>
> It is very unlikely that there will be a build tomorrow, Stephen will be
> back and -next will be back to normal on Monday.

Thank you very much for taking this on again.  I am back and hopefully
will be able to take over from where you got to.

I will try very hard not to send emails about the conflicts/build
problems you have already noted, but there may be some overlap.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web