Re: linux-next: Tree for Nov 3 (drivers/net/ethernet/marvell/prestera/prestera_switchdev.o)

Hi Randy, Randy Dunlap writes: > On 11/2/20 11:19 PM, Stephen Rothwell wrote: >> Hi all, >> >> Changes since 20201102: >> > > on x86_64: > > when CONFIG_BRIDGE=m: > > ld: drivers/net/ethernet/marvell/prestera/prestera_switchdev.o: in function > `prestera_bridge_port_event': >

Re: linux-next: Tree for Nov 3 (drivers/net/ethernet/marvell/prestera/prestera_switchdev.o)

On 11/2/20 11:19 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20201102: > on x86_64: when CONFIG_BRIDGE=m: ld: drivers/net/ethernet/marvell/prestera/prestera_switchdev.o: in function `prestera_bridge_port_event': prestera_switchdev.c:(.text+0x2ebd): undefined reference to

linux-next: Tree for Nov 3

Hi all, Changes since 20201102: The imx-mxs tree gained a build failure for which I reverted a commit. The f2fs tree gained a build failure so I used the version from next-20201102. The amdgpu tree gained a conflict against Linus' tree. The drm-misc tree gained a conflict against the amdgpu

Re: linux-next: Tree for Nov 3

On Fri, Nov 3, 2017 at 2:28 AM, Stephen Rothwell wrote: > Non-merge commits (relative to Linus' tree): 10201 > 9162 files changed, 500400 insertions(+), 233533 deletions(-) We're close enough with the timer_setup() conversion[1] that I thought I might start providing a

Re: linux-next: Tree for Nov 3

On Fri, Nov 3, 2017 at 2:28 AM, Stephen Rothwell wrote: > Non-merge commits (relative to Linus' tree): 10201 > 9162 files changed, 500400 insertions(+), 233533 deletions(-) We're close enough with the timer_setup() conversion[1] that I thought I might start providing a status update. As of this

linux-next: Tree for Nov 3

Hi all, Changes since 20171102: New tree: opp The SPDX license identifier addition commits in Linus' tree caused 81 new conflicts in linux-next today, but I did not report them as the resolutions are trivial and most of them are files that are removed in linux-next. The sunxi tree lost its

linux-next: Tree for Nov 3

Hi all, Changes since 20171102: New tree: opp The SPDX license identifier addition commits in Linus' tree caused 81 new conflicts in linux-next today, but I did not report them as the resolutions are trivial and most of them are files that are removed in linux-next. The sunxi tree lost its

linux-next: Tree for Nov 3

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 20151102: The pci tree lost its build failure. The net-next tree gained a conflict against the net tree. The battery tree still had its build

linux-next: Tree for Nov 3

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 20151102: The pci tree lost its build failure. The net-next tree gained a conflict against the net tree. The battery tree still had its build

Re: linux-next: Tree for Nov 3

Hi Guenter, On Mon, 3 Nov 2014 13:50:01 -0800 Guenter Roeck wrote: > > Something is fishy with this tree. I get either warnings or complete failures > with qemu runs on all platforms. > > x86_64: > > [ cut here ] > WARNING: CPU: 0 PID: 1 at fs/dcache.c:255

Re: linux-next: Tree for Nov 3

On Mon, Nov 03, 2014 at 04:14:03PM +1100, Stephen Rothwell wrote: > Hi all, > > Changes since 20141031: > > Linus' tree gained a build failure for which I applied a patch. > > The staging tree gained conflicts against the vfs tree. > > The scsi tree gained a build failure so I used the version

Re: linux-next: Tree for Nov 3

On Mon, Nov 03, 2014 at 04:14:03PM +1100, Stephen Rothwell wrote: Hi all, Changes since 20141031: Linus' tree gained a build failure for which I applied a patch. The staging tree gained conflicts against the vfs tree. The scsi tree gained a build failure so I used the version from

Re: linux-next: Tree for Nov 3

Hi Guenter, On Mon, 3 Nov 2014 13:50:01 -0800 Guenter Roeck li...@roeck-us.net wrote: Something is fishy with this tree. I get either warnings or complete failures with qemu runs on all platforms. x86_64: [ cut here ] WARNING: CPU: 0 PID: 1 at fs/dcache.c:255

linux-next: Tree for Nov 3

Hi all, Changes since 20141031: Linus' tree gained a build failure for which I applied a patch. The staging tree gained conflicts against the vfs tree. The scsi tree gained a build failure so I used the version from next-20141031. The akpm-current tree lost its build failure. Non-merge

linux-next: Tree for Nov 3

Hi all, Changes since 20141031: Linus' tree gained a build failure for which I applied a patch. The staging tree gained conflicts against the vfs tree. The scsi tree gained a build failure so I used the version from next-20141031. The akpm-current tree lost its build failure. Non-merge