RE: linux-next: Tree for Dec 9 (usb/cdns3)

2020-12-10 Thread Pawel Laszczak
Peter, > >> >>> >>>On 20-12-09 16:58:16, Randy Dunlap wrote: On 12/9/20 2:44 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20201208: > (I don't know what to do about this one -- seeking help.) >>> >>>Add Pawel. >>> >>>Hi Pawel, >>> >>>Add old cdns3 logi

RE: linux-next: Tree for Dec 9 (usb/cdns3)

2020-12-10 Thread Pawel Laszczak
Peter, > >> >>On 20-12-09 16:58:16, Randy Dunlap wrote: >>> On 12/9/20 2:44 AM, Stephen Rothwell wrote: >>> > Hi all, >>> > >>> > Changes since 20201208: >>> > >>> >>> (I don't know what to do about this one -- seeking help.) >> >>Add Pawel. >> >>Hi Pawel, >> >>Add old cdns3 logic, when the CONFIG

RE: linux-next: Tree for Dec 9 (usb/cdns3)

2020-12-10 Thread Pawel Laszczak
> >On 20-12-09 16:58:16, Randy Dunlap wrote: >> On 12/9/20 2:44 AM, Stephen Rothwell wrote: >> > Hi all, >> > >> > Changes since 20201208: >> > >> >> (I don't know what to do about this one -- seeking help.) > >Add Pawel. > >Hi Pawel, > >Add old cdns3 logic, when the CONFIG_USB=m >If CONFIG_USB_C

Re: linux-next: Tree for Dec 9 (usb/cdns3)

2020-12-10 Thread Peter Chen
On 20-12-09 16:58:16, Randy Dunlap wrote: > On 12/9/20 2:44 AM, Stephen Rothwell wrote: > > Hi all, > > > > Changes since 20201208: > > > > (I don't know what to do about this one -- seeking help.) Add Pawel. Hi Pawel, Add old cdns3 logic, when the CONFIG_USB=m If CONFIG_USB_CDNS3 is M, the h

Re: linux-next: Tree for Dec 9 (usb/cdns3)

2020-12-09 Thread Randy Dunlap
On 12/9/20 2:44 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20201208: > (I don't know what to do about this one -- seeking help.) on x86_64: ld: drivers/usb/cdns3/host.o: in function `xhci_cdns3_suspend_quirk': host.c:(.text+0x9): undefined reference to `usb_hcd_is_primary_hcd' T

Re: linux-next: Tree for Dec 9 (ethernet/mellanox/mlx5)

2020-12-09 Thread Stephen Rothwell
Hi all, On Wed, 9 Dec 2020 12:14:39 -0800 Randy Dunlap wrote: > > On 12/9/20 2:44 AM, Stephen Rothwell wrote: > > Hi all, > > > > Changes since 20201208: > > > > on i386: > > I see this warning:/note: repeated 106 times on i386 build: > > from ../drivers/net/ethernet/mella

Re: linux-next: Tree for Dec 9 (ethernet/mellanox/mlx5)

2020-12-09 Thread Randy Dunlap
On 12/9/20 2:44 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20201208: > on i386: I see this warning:/note: repeated 106 times on i386 build: from ../drivers/net/ethernet/mellanox/mlx5/core/alloc.c:34: ../include/vdso/bits.h:7:26: warning: left shift count >= width

Re: linux-next: Tree for Dec 9

2020-12-09 Thread John Garry
On 09/12/2020 10:44, Stephen Rothwell wrote: Hi all, Changes since 20201208: Just seeing this today: john@localhost:~/linux-next> git checkout next-20201209 Previous HEAD position was bfd521e1af51 Add linux-next specific files for 20201203 HEAD is now at 2f1d5c77f13f Add linux-next specific

linux-next: Tree for Dec 9

2020-12-09 Thread Stephen Rothwell
Hi all, Changes since 20201208: The pm tree gained a build failure when building htmldocs. The wireless-drivers-next tree lost its build failure. The nand tree still had its build failure so I used the version from next-20201207. The drm tree gained a semantic conflict against the drm-intel-fi

linux-next: Tree for Dec 9

2016-12-08 Thread Stephen Rothwell
Hi all, Changes since 20161208: The pci tree gained a conflict against Linus' tree. The spi tree gained a build failure so I used the version from next-20161208. The tip tree gained a conflict against the pci tree. Non-merge commits (relative to Linus' tree): 10377 9526 files changed, 656932

Re: the first bad commit "use memblock_insert_region() for the empty array" (was linux-next: Tree for Dec 9)

2015-12-09 Thread Andy Shevchenko
On Wed, Dec 9, 2015 at 2:02 PM, Sergey Senozhatsky wrote: > Hello, > > On (12/09/15 17:59), Sergey Senozhatsky wrote: >> On (12/09/15 18:19), Stephen Rothwell wrote: >> > >> > Changes since 20151208: >> > >> >> corrupts low memory: Oh, I have to check for this first, I did the same bisect and fou

Re: the first bad commit "use memblock_insert_region() for the empty array" (was linux-next: Tree for Dec 9)

2015-12-09 Thread Sergey Senozhatsky
Hello, On (12/09/15 17:59), Sergey Senozhatsky wrote: > On (12/09/15 18:19), Stephen Rothwell wrote: > > > > Changes since 20151208: > > > > corrupts low memory: > > [ 60.459441] Corrupted low memory at 88001000 (1000 phys) = 0001 > [ 60.459445] Corrupted low memory at 8800

Re: linux-next: Tree for Dec 9

2015-12-09 Thread Sergey Senozhatsky
Hello, On (12/09/15 18:19), Stephen Rothwell wrote: > > Changes since 20151208: > corrupts low memory: [ 60.459441] Corrupted low memory at 88001000 (1000 phys) = 0001 [ 60.459445] Corrupted low memory at 88001008 (1008 phys) = 81a816b8 [ 60.459446] Corrupted

linux-next: Tree for Dec 9

2015-12-08 Thread Stephen Rothwell
Hi all, Changes since 20151208: The vfs tree lost its build failure but gained another for which I applied a merge fix patch and yet another for which I applied a fix patch. The pm tree gained a build failure so I used the version from next-20151208. The drm tree gained a conflict against the d

linux-next: Tree for Dec 9

2014-12-09 Thread Stephen Rothwell
Hi all, Changes since 20141208: Dropped tree: access_once The thermal tree gained a build failure so I used the version from next-20141208. The slave-dma tree gained a conflict against the arm tree. The spi tree lost its build failures. The rcu tree gained a build failure for which I reverted

linux-next: Tree for Dec 9

2013-12-08 Thread Stephen Rothwell
Hi all, Changes since 20131206: The powerpc tree gained a build failure for which I reverted some commits. The crypto tree still had its build failure so I used the version from next-20131205. The driver-core tree gained a conflict against the driver-core.current tree. The usb-gadget tree gain