From: Randy Dunlap Sent: Wednesday, February 27, 2019
9:25 AM
>
> on i386:
>
> ../arch/x86/kernel/cpu/mshyperv.c: In function 'ms_hyperv_init_platform':
> ../arch/x86/kernel/cpu/mshyperv.c:339:3: error: 'x2apic_phys' undeclared
> (first use in this
> function)
>x2apic_phys = 1;
>^
On 2/26/19 10:44 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190226:
>
on i386:
../arch/x86/kernel/cpu/mshyperv.c: In function ‘ms_hyperv_init_platform’:
../arch/x86/kernel/cpu/mshyperv.c:339:3: error: ‘x2apic_phys’ undeclared (first
use in this function)
x2apic_phys = 1;
Hi all,
Changes since 20190226:
The mmc-fixes tree still has its build failure for which I reverted a commit.
The hwmon-staging tree lost its build failure.
The net-next tree gained a conflict against the rdma tree.
The vhost tree gained a conflict against the iommu tree.
Non-merge commits
Hi all,
Changes since 20180226:
The akpm-current tree gained conflicts against the ext3 tree.
Non-merge commits (relative to Linus' tree): 3516
4224 files changed, 161343 insertions(+), 103609 deletions(-)
I have
Hi all,
Changes since 20180226:
The akpm-current tree gained conflicts against the ext3 tree.
Non-merge commits (relative to Linus' tree): 3516
4224 files changed, 161343 insertions(+), 103609 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 20170224:
The vfs tree gained conflicts agains Linus' and the f2fs trees and a
build failure for which I added a fix patch.
The drm tree lost
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 20170224:
The vfs tree gained conflicts agains Linus' and the f2fs trees and a
build failure for which I added a fix patch.
The drm tree lost
On Fri, 2015-02-27 at 11:59 -0800, Guenter Roeck wrote:
> On Fri, Feb 27, 2015 at 03:49:17PM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20150226:
> >
> > New Tree: rpi
> >
> > The drm-intel tree gained a conflict against the drm-intel-fixes tree.
> >
> > The rcu tree
On Fri, Feb 27, 2015 at 03:49:17PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150226:
>
> New Tree: rpi
>
> The drm-intel tree gained a conflict against the drm-intel-fixes tree.
>
> The rcu tree gained a build failure so I used the version from
> next-20150226.
>
> The clk
On Fri, Feb 27, 2015 at 03:49:17PM +1100, Stephen Rothwell wrote:
Hi all,
Changes since 20150226:
New Tree: rpi
The drm-intel tree gained a conflict against the drm-intel-fixes tree.
The rcu tree gained a build failure so I used the version from
next-20150226.
The clk tree lost
On Fri, 2015-02-27 at 11:59 -0800, Guenter Roeck wrote:
On Fri, Feb 27, 2015 at 03:49:17PM +1100, Stephen Rothwell wrote:
Hi all,
Changes since 20150226:
New Tree: rpi
The drm-intel tree gained a conflict against the drm-intel-fixes tree.
The rcu tree gained a build failure
Hi all,
Changes since 20150226:
New Tree: rpi
The drm-intel tree gained a conflict against the drm-intel-fixes tree.
The rcu tree gained a build failure so I used the version from
next-20150226.
The clk tree lost its build failure but gained another so I used the
version from next-20150225.
Hi all,
Changes since 20150226:
New Tree: rpi
The drm-intel tree gained a conflict against the drm-intel-fixes tree.
The rcu tree gained a build failure so I used the version from
next-20150226.
The clk tree lost its build failure but gained another so I used the
version from next-20150225.
Hi all,
This tree fails (more than usual) the powerpc allyesconfig build.
Changes since 20140226:
The powerpc tree still had its build failure.
The libata tree lost its build failure.
The mfd-lj tree still had its build failure so I used the version from
next-20140210.
The drm-tegra tree
Hi all,
This tree fails (more than usual) the powerpc allyesconfig build.
Changes since 20140226:
The powerpc tree still had its build failure.
The libata tree lost its build failure.
The mfd-lj tree still had its build failure so I used the version from
next-20140210.
The drm-tegra tree
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 20130226:
The drm tree lost its build failure.
The renesas tree gained a conflict against Linus' tree.
The akpm tree gained a conflict against the vfs
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 20130226:
The drm tree lost its build failure.
The renesas tree gained a conflict against Linus' tree.
The akpm tree gained a conflict against the vfs
17 matches
Mail list logo
