On 12/17/20 9:33 PM, Stephen Rothwell wrote:
> Hi all,
>
> News: there will be no linux-next releases between Dec 24 and Jan
> 3 inclusive.
>
> Please do not add any v5.12 destined code to your linux-next included
> branches until after v5.11-rc1 has been released.
>
> Changes since 20201217:
>
Hi all,
News: there will be no linux-next releases between Dec 24 and Jan
3 inclusive.
Please do not add any v5.12 destined code to your linux-next included
branches until after v5.11-rc1 has been released.
Changes since 20201217:
The ext4 tree gained a conflict against Linus' tree.
The
Hi all,
Changes since 20181217:
The nfs-anna tree lost its build failure.
The vfs tree gained a conflict against the fscrypt tree.
The hwmon-staging tree lost its build failure.
The rdma tree still had its build failure so I used a supplied patch.
The net-next tree lost its build failure.
Hi all,
Changes since 20171215:
The staging.current tree lost its build failure.
The tty tree gained a build failure so I used the version from
next-20171215.
The akpm-current tree gained a conflict against the tip tree.
The akpm tree lost a couple of patches that turned up elsewhere.
Hi all,
Changes since 20171215:
The staging.current tree lost its build failure.
The tty tree gained a build failure so I used the version from
next-20171215.
The akpm-current tree gained a conflict against the tip tree.
The akpm tree lost a couple of patches that turned up elsewhere.
Hi all,
Changes since 20151217:
News: The arm defconfig build is fixed again.
The arm-soc tree lost its build failure.
The i2c tree still had its build failure for which I applied a patch.
The clockevents tree still had its build failure so I used the version
from next-20151216.
The pinctrl
Hi all,
Changes since 20151217:
News: The arm defconfig build is fixed again.
The arm-soc tree lost its build failure.
The i2c tree still had its build failure for which I applied a patch.
The clockevents tree still had its build failure so I used the version
from next-20151216.
The pinctrl
Hi all,
There will only be intermittent releases of linux-next between now and
Jan 5.
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 20141217:
The modules tree gained a build failure so I merged a
Hi all,
There will only be intermittent releases of linux-next between now and
Jan 5.
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 20141217:
The modules tree gained a build failure so I merged a
Hi all,
Changes since 20131217:
Linus' tree lost its build failure.
The powerpc tree still had its build failure for which I applied a
supplied patch.
The pm tree gained a build failure so I used the version from
next-20131217.
The net-next tree gained a conflict against Linus' tree and a
Hi all,
Changes since 20131217:
Linus' tree lost its build failure.
The powerpc tree still had its build failure for which I applied a
supplied patch.
The pm tree gained a build failure so I used the version from
next-20131217.
The net-next tree gained a conflict against Linus' tree and a
Hi all,
Changes since 20121217:
Lots of conflicts are migrating between trees.
The btrfs tree lost its build failure.
The akpm tree gained a build failure for which I applied a patch.
I have created today's
Hi all,
Changes since 20121217:
Lots of conflicts are migrating between trees.
The btrfs tree lost its build failure.
The akpm tree gained a build failure for which I applied a patch.
I have created today's
13 matches
Mail list logo
