Hi all,
Changes since 20190227:
The mmc-fixes tree lost its build failure.
The bpf-next tree gained a build failure for which I applied a hackisk
patch.
The staging tree gained a conflict against the net-next tree.
Non-merge commits (relative to Linus' tree): 10428
10406 files changed,
Hi all,
Changes since 20180227:
The net-next tree gained a conflict against the net tree.
Non-merge commits (relative to Linus' tree): 3753
4443 files changed, 168483 insertions(+), 107955 deletions(-)
I have
Hi all,
Changes since 20180227:
The net-next tree gained a conflict against the net tree.
Non-merge commits (relative to Linus' tree): 3753
4443 files changed, 168483 insertions(+), 107955 deletions(-)
I have
Hi all,
Please do not add any material intended for v4.12 to your linux-next
included branches until after v4.11-rc1 has been released.
Changes since 20170227:
The vfs tree still had its build failure for which I added a fix patch.
The scsi tree lost its build failure.
Non-merge commits
Hi all,
Please do not add any material intended for v4.12 to your linux-next
included branches until after v4.11-rc1 has been released.
Changes since 20170227:
The vfs tree still had its build failure for which I added a fix patch.
The scsi tree lost its build failure.
Non-merge commits
Hi all,
This tree fails (more than usual) the powerpc allyesconfig build.
Changes since 20140227:
The powerpc tree still had its build failure.
The mfd-lj tree still had its build failure so I used the version from
next-20140210.
The drm-tegra tree lost its build failure.
The wireless-next
Hi all,
This tree fails (more than usual) the powerpc allyesconfig build.
Changes since 20140227:
The powerpc tree still had its build failure.
The mfd-lj tree still had its build failure so I used the version from
next-20140210.
The drm-tegra tree lost its build failure.
The wireless-next
On Thu, Feb 28, 2013 at 10:51:48AM -0800, Randy Dunlap wrote:
> Also, drivers/md/Kconfig contains "select DM_PRISON" but there is no
> DM_PRISON defined anywhere that I can find...
Thanks! Hopefully fixed now: It's DM_BIO_PRISON.
Alasdair
--
To unsubscribe from this list: send the line
On 02/27/13 18:27, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any work destined for v3.10 to your -next included
> branches until after Linus has release v3.9-rc1.
>
> Changes since 20130227:
>
> The device-mapper tree gained a build failure for which I applied a patch.
>
on
On 02/27/13 18:27, Stephen Rothwell wrote:
Hi all,
Please do not add any work destined for v3.10 to your -next included
branches until after Linus has release v3.9-rc1.
Changes since 20130227:
The device-mapper tree gained a build failure for which I applied a patch.
on x86_64 or
On Thu, Feb 28, 2013 at 10:51:48AM -0800, Randy Dunlap wrote:
Also, drivers/md/Kconfig contains select DM_PRISON but there is no
DM_PRISON defined anywhere that I can find...
Thanks! Hopefully fixed now: It's DM_BIO_PRISON.
Alasdair
--
To unsubscribe from this list: send the line unsubscribe
Hi all,
Please do not add any work destined for v3.10 to your -next included
branches until after Linus has release v3.9-rc1.
Changes since 20130227:
The device-mapper tree gained a build failure for which I applied a patch.
The akpm tree gained a build failure for which I applied a patch and
Hi all,
Please do not add any work destined for v3.10 to your -next included
branches until after Linus has release v3.9-rc1.
Changes since 20130227:
The device-mapper tree gained a build failure for which I applied a patch.
The akpm tree gained a build failure for which I applied a patch and
13 matches
Mail list logo
