Hi all,
Changes since 20201214:
The ceph tree gained a semantic conflict against Linus' tree.
The nfs tree gained a conflict agsinst Linus' tree.
The cel tree gained conflicts agsinst the nfs tree.
The thermal tree gained a build failure so I used the version from
next-20101214.
The keys tree
Hi Sergey,
On Fri, 15 Dec 2017 15:54:22 +0900 Sergey Senozhatsky
wrote:
>
> hm, still no next-20171215 at
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/refs/
It seems that the mirroring has failed, as the backend has been updated
correctly (I even did it again but it wa
Hello,
On (12/15/17 15:13), Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20171214:
>
> New tree: init_task
>
> The staging.current tree still had its build failure for which I reverted
> a commit.
hm, still no next-20171215 at
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
Hi all,
Changes since 20171214:
New tree: init_task
The staging.current tree still had its build failure for which I reverted
a commit.
Non-merge commits (relative to Linus' tree): 4569
4982 files changed, 156683 insertions(+), 143157 deletions(-)
-
Randy,
On 15.12.2016 19:13, Randy Dunlap wrote:
> On 12/14/16 19:21, Stephen Rothwell wrote:
>> Hi all,
>>
>> Please do not add any material for v4.11 to your linux-next included
>> branches until after v4.10-rc1 has been released.
>>
>> Changes since 20161214:
>>
>
> on x86_64:
>
> when CONFIG_
On 12/14/16 19:21, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any material for v4.11 to your linux-next included
> branches until after v4.10-rc1 has been released.
>
> Changes since 20161214:
>
on x86_64:
when CONFIG_BLOCK is not enabled:
warning: (UBIFS_FS_ENCRYPTION) selects F
Hi all,
Please do not add any material for v4.11 to your linux-next included
branches until after v4.10-rc1 has been released.
Changes since 20161214:
The btrfs-kdave tree gained a conflict against Linus' tree.
The rdma tree gained a conflict against Linus' tree.
Non-merge commits (relative to
Hi all,
Changes since 20151214:
The samsung-krzk tree gained a conflict against the renesas tree.
The net-next tree gained a conflict against the net tree.
The drm-msm tree gained a build failure for which I applied a merge
fix patch.
The akpm-current tree gained a conflict against the powerpc
Hi all,
Please do not add any code destined for v3.20 to your linux-next included
trees/branches until after v3.19-rc1 is released.
Changes since 20141212:
The tip tree gained a conflict against the pm tree.
The rcu tree lost its build failure.
The driver-core tree gained conflicts against Lin
9 matches
Mail list logo
