Hi all,
Changes since 20181218:
New tree: kgdb-dt
The rdma tree still had its build failure so I used a supplied patch.
The kvm tree gained a conflict against the tip tree and a build failure
for which I applied a merge fix patch.
Non-merge commits (relative to Linus' tree): 9805
10005 files
Hi all,
Changes since 20171218:
The xtensa tree gained a conflict against Linus' tree.
The v4l-dvb tree gained a conflict against the vfs tree.
The net-next tree gained a conflict against the net tree.
The tty tree lost its build failure.
Non-merge commits (relative to Linus' tree): 4879
Hi all,
Changes since 20171218:
The xtensa tree gained a conflict against Linus' tree.
The v4l-dvb tree gained a conflict against the vfs tree.
The net-next tree gained a conflict against the net tree.
The tty tree lost its build failure.
Non-merge commits (relative to Linus' tree): 4879
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 20161216:
New tree: target-bva
The overlayfs tree gained conflicts against Linus' tree.
The kvm tree gained a build failure so I used the version from
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 20161216:
New tree: target-bva
The overlayfs tree gained conflicts against Linus' tree.
The kvm tree gained a build failure so I used the version from
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.
There will only be intermittent releases of linux-next between now and
Jan 5.
Changes since 20141218:
The modules tree lost its build failure.
Non-merge commits
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.
There will only be intermittent releases of linux-next between now and
Jan 5.
Changes since 20141218:
The modules tree lost its build failure.
Non-merge commits
On Thu, 2013-12-19 at 11:32 -0800, Randy Dunlap wrote:
> On 12/18/13 21:51, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20131218:
> >
>
>
> on i386:
>
> drivers/built-in.o: In function `target_alua_state_check':
> (.text+0x3fc859): undefined reference to `__udivdi3'
>
>
Mmm,
On Thu, Dec 19, 2013 at 8:32 PM, Randy Dunlap wrote:
> On 12/18/13 21:51, Stephen Rothwell wrote:
>> Changes since 20131218:
> on i386:
>
> drivers/built-in.o: In function `target_alua_state_check':
> (.text+0x3fc859): undefined reference to `__udivdi3'
I believe this is already fixed in today's
On 12/18/13 21:51, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20131218:
>
on i386:
drivers/built-in.o: In function `target_alua_state_check':
(.text+0x3fc859): undefined reference to `__udivdi3'
--
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On 12/18/13 21:51, Stephen Rothwell wrote:
Hi all,
Changes since 20131218:
on i386:
drivers/built-in.o: In function `target_alua_state_check':
(.text+0x3fc859): undefined reference to `__udivdi3'
--
~Randy
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
On Thu, Dec 19, 2013 at 8:32 PM, Randy Dunlap rdun...@infradead.org wrote:
On 12/18/13 21:51, Stephen Rothwell wrote:
Changes since 20131218:
on i386:
drivers/built-in.o: In function `target_alua_state_check':
(.text+0x3fc859): undefined reference to `__udivdi3'
I believe this is already
On Thu, 2013-12-19 at 11:32 -0800, Randy Dunlap wrote:
On 12/18/13 21:51, Stephen Rothwell wrote:
Hi all,
Changes since 20131218:
on i386:
drivers/built-in.o: In function `target_alua_state_check':
(.text+0x3fc859): undefined reference to `__udivdi3'
Mmm, this appears to
Hi all,
Changes since 20131218:
The powerpc tree still had its build failure for which I applied a
supplied patch.
The pm tree lost its build failure.
The net-next tree gained a new build failure so I used the version from
next-20131217.
The drm tree gained conflicts against Linus' tree.
The
Hi all,
Changes since 20131218:
The powerpc tree still had its build failure for which I applied a
supplied patch.
The pm tree lost its build failure.
The net-next tree gained a new build failure so I used the version from
next-20131217.
The drm tree gained conflicts against Linus' tree.
The
Hi all,
Changes since 20121218:
Removed tree: i2c (new maintainer)
Lots of conflicts are migrating between trees.
The slave-dma tree gained a conflict against Linus' tree.
The modules tree gained a conflict against Linus' tree.
The fsnotify tree gained a build failure for which I applied a
Hi all,
Changes since 20121218:
Removed tree: i2c (new maintainer)
Lots of conflicts are migrating between trees.
The slave-dma tree gained a conflict against Linus' tree.
The modules tree gained a conflict against Linus' tree.
The fsnotify tree gained a build failure for which I applied a
17 matches
Mail list logo
