Re: linux-next: Tree for May 7 (hid/hid-asus)

2020-05-07 Thread Jiri Kosina
On Thu, 7 May 2020, Randy Dunlap wrote: > > Changes since 20200505: > > > > > on i386 or x86_64: > > ERROR: modpost: "usb_hid_driver" [drivers/hid/hid-asus.ko] undefined! > or > (when builtin:) > ld: drivers/hid/hid-asus.o: in function `asus_probe': > hid-asus.c:(.text+0x60f): undefined refere

Re: linux-next: Tree for May 7 (hid/hid-asus)

2020-05-07 Thread Randy Dunlap
On 5/7/20 1:15 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20200505: > on i386 or x86_64: ERROR: modpost: "usb_hid_driver" [drivers/hid/hid-asus.ko] undefined! or (when builtin:) ld: drivers/hid/hid-asus.o: in function `asus_probe': hid-asus.c:(.text+0x60f): undefined reference to

Re: linux-next: Tree for May 7 (net/xdp)

2018-05-07 Thread Randy Dunlap
On 05/06/2018 10:31 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20180504: > on i386: net/xdp/xdp_umem.o: In function `xdp_umem_reg': xdp_umem.c:(.text+0x47e): undefined reference to `__udivdi3' -- ~Randy

Re: linux-next: Tree for May 7

2018-05-07 Thread Stephen Rothwell
Hi Geert, On Mon, 7 May 2018 14:13:27 +0200 Geert Uytterhoeven wrote: > > On Mon, May 7, 2018 at 7:31 AM, Stephen Rothwell > wrote: > > Status of my local build tests will be at > > http://kisskb.ellerman.id.au/linux-next . > > Oops, Service Unavailable I restarted docker and it seems to h

Re: linux-next: Tree for May 7

2018-05-07 Thread Geert Uytterhoeven
Hi Stephen, On Mon, May 7, 2018 at 7:31 AM, Stephen Rothwell wrote: > Status of my local build tests will be at > http://kisskb.ellerman.id.au/linux-next . Oops, Service Unavailable Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 --

Re: linux-next: Tree for May 7 (openrisc, sparc qemu BUG due to 'hrtimer: Get rid of hrtimer softirq')

2015-05-07 Thread Geert Uytterhoeven
On Fri, May 8, 2015 at 3:54 AM, Guenter Roeck wrote: > On Thu, May 07, 2015 at 04:47:15PM +1000, Stephen Rothwell wrote: >> Hi all, >> >> Changes since 20150506: >> >> The ext4 tree gained a build failure so I used the version from >> next-20150506. >> >> The vfs tree gained a conflict against the

Re: linux-next: Tree for May 7 (openrisc, sparc qemu BUG due to 'hrtimer: Get rid of hrtimer softirq')

2015-05-07 Thread Guenter Roeck
On Thu, May 07, 2015 at 04:47:15PM +1000, Stephen Rothwell wrote: > Hi all, > > Changes since 20150506: > > The ext4 tree gained a build failure so I used the version from > next-20150506. > > The vfs tree gained a conflict against the f2fs tree. > > The rcu tree gained conflicts against the ti

Re: linux-next: Tree for May 7 (avr32 build failure)

2015-05-07 Thread Guenter Roeck
On Thu, May 07, 2015 at 04:47:15PM +1000, Stephen Rothwell wrote: > Hi all, > > Changes since 20150506: > > The ext4 tree gained a build failure so I used the version from > next-20150506. > > The vfs tree gained a conflict against the f2fs tree. > > The rcu tree gained conflicts against the ti

Re: linux-next: Tree for May 7 (argh)

2014-05-07 Thread Randy Dunlap
On 05/07/2014 02:56 PM, Stephen Rothwell wrote: > Hi Randy, > > On Wed, 07 May 2014 13:52:02 -0700 Randy Dunlap wrote: >> >> I was away for one week. Did I miss some new instructions about >> building linux-next? > > Nothing that I know of. > >> >> I get a thousands of messages like these: >

Re: linux-next: Tree for May 7 (argh)

2014-05-07 Thread Stephen Rothwell
Hi Randy, On Wed, 07 May 2014 13:52:02 -0700 Randy Dunlap wrote: > > I was away for one week. Did I miss some new instructions about > building linux-next? Nothing that I know of. > > I get a thousands of messages like these: What config? What arch? Did you just do "make oldconfig"? > WAR

Re: linux-next: Tree for May 7 (argh)

2014-05-07 Thread Randy Dunlap
On 05/07/2014 12:33 AM, Stephen Rothwell wrote: > Hi all, > > This tree still fails (more than usual) the powerpc allyesconfig build > and also the celleb_defconfig. > > Changes since 20140506: > I was away for one week. Did I miss some new instructions about building linux-next? I get a thou

Re: linux-next: Tree for May 7 (bq27x00_battery)

2013-05-10 Thread Anton Vorontsov
On Tue, May 07, 2013 at 10:21:21AM -0700, Randy Dunlap wrote: > On 05/06/13 20:49, Stephen Rothwell wrote: > > Hi all, > > > > Please do not add any v3.11 destined work to your linux-next included > > branches until after v3.10-rc1 is released. > > > > I am receiving a (un)reasonable number of co

Re: linux-next: Tree for May 7 (iio)

2013-05-07 Thread Lars-Peter Clausen
On 05/07/2013 07:08 PM, Randy Dunlap wrote: > On 05/06/13 20:49, Stephen Rothwell wrote: >> Hi all, >> >> Please do not add any v3.11 destined work to your linux-next included >> branches until after v3.10-rc1 is released. >> >> I am receiving a (un)reasonable number of conflicts from there being >

Re: linux-next: Tree for May 7 (bq27x00_battery)

2013-05-07 Thread Randy Dunlap
On 05/06/13 20:49, Stephen Rothwell wrote: > Hi all, > > Please do not add any v3.11 destined work to your linux-next included > branches until after v3.10-rc1 is released. > > I am receiving a (un)reasonable number of conflicts from there being > multiple copies of some commits in various trees.

Re: linux-next: Tree for May 7 (iio)

2013-05-07 Thread Randy Dunlap
On 05/06/13 20:49, Stephen Rothwell wrote: > Hi all, > > Please do not add any v3.11 destined work to your linux-next included > branches until after v3.10-rc1 is released. > > I am receiving a (un)reasonable number of conflicts from there being > multiple copies of some commits in various trees.

Re: linux-next: Tree for May 7 (usb/chipidea)

2013-05-07 Thread Randy Dunlap
On 05/06/13 20:49, Stephen Rothwell wrote: > Hi all, > > Please do not add any v3.11 destined work to your linux-next included > branches until after v3.10-rc1 is released. > > I am receiving a (un)reasonable number of conflicts from there being > multiple copies of some commits in various trees.