Hi all,
Changes since 20201112:
The drivers-memory tree still had its build failure.
The ext3 tree gained a build failure so I used the version from
next-20201112.
The usb-chipidea-next tree gained a build failure for which I reverted
a commit.
The akpm tree gained a build failure for which I
Hi all,
Changes since 20181112:
The kbuild tree gained a conflict against the kbuild-current tree.
The tip tree still had its build failure for which I applied a fix patch.
Non-merge commits (relative to Linus' tree): 2535
2699 files changed, 105795 insertions(+), 93590 deletions(-)
-
Hi all,
Please do not add any v4.16 material to your linux-next included trees
until v4.15-rc1 has been released.
Changes since 20171110:
The powerpc tree still had its build failure for which I applied a
patch
The keys tree gained a build failure so I used the version from
next-20171110.
Non-
On 11/12/15 18:23, Stephen Rothwell wrote:
> Hi all,
>
> Please do *not* add any material intended for v4.5 to your linux-next
> included branches until after v4.4-rc1 has been released.
>
> Changes since 20151112:
>
on x86_64:
net/built-in.o: In function `tee_tg6':
xt_TEE.c:(.text+0x4b28b):
Hi all,
Please do *not* add any material intended for v4.5 to your linux-next
included branches until after v4.4-rc1 has been released.
Changes since 20151112:
Dropped tree: target-merge (many conflicts)
The clockevents tree gained a conflict against the h8300 tree.
The scsi tree gained a buil
On Thu, Nov 13, 2014 at 06:10:02PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20141112:
>
> The net-next tree gained a conflict against the net tree.
>
> The mfd tree gained a conflict against Linus' tree.
>
> The akpm-current tree lost its build failures.
>
> Non-merge commits
Hi all,
Changes since 20141112:
The net-next tree gained a conflict against the net tree.
The mfd tree gained a conflict against Linus' tree.
The akpm-current tree lost its build failures.
Non-merge commits (relative to Linus' tree): 6008
6314 files changed, 193590 insertions(+), 163738 delet
Hi all,
Please do *not* add any v3.14 material to linux-next until after
v3.13-rc1 is released.
Changes since 20131112:
The aio-direct tree gained a conflict against the btrfs tree.
I have created today's linux-next t
Hi all,
News: next-20121115 will be the last release until next-20121126 (which
should be just be after -rc7, I guess - assuming that Linus does not
release v3.7 before then), so if you want something in linux-next for a
reasonable amount of testing, it should probably be committed in the next
day
9 matches
Mail list logo
