Re: linux-next: Tree for Oct 31 (vboxguest)

2018-11-04 Thread Masahiro Yamada
On Mon, Nov 5, 2018 at 9:54 AM Changbin Du wrote: > > On Sun, Nov 04, 2018 at 11:43:44AM +0900, Masahiro Yamada wrote: > > On Sat, Nov 3, 2018 at 12:55 AM Arnd Bergmann wrote: > > > > > > On 11/2/18, Masahiro Yamada wrote: > > > > On Thu, Nov 1, 2018 at 11:32 PM Changbin Du > > > > wrote: > >

Re: linux-next: Tree for Oct 31 (vboxguest)

2018-11-04 Thread Changbin Du
On Sun, Nov 04, 2018 at 11:43:44AM +0900, Masahiro Yamada wrote: > On Sat, Nov 3, 2018 at 12:55 AM Arnd Bergmann wrote: > > > > On 11/2/18, Masahiro Yamada wrote: > > > On Thu, Nov 1, 2018 at 11:32 PM Changbin Du wrote: > > >> On Thu, Nov 01, 2018 at 12:32:48PM +0900, Masahiro Yamada wrote: > >

Re: linux-next: Tree for Oct 31 (vboxguest)

2018-11-03 Thread Masahiro Yamada
On Sat, Nov 3, 2018 at 12:55 AM Arnd Bergmann wrote: > > On 11/2/18, Masahiro Yamada wrote: > > On Thu, Nov 1, 2018 at 11:32 PM Changbin Du wrote: > >> On Thu, Nov 01, 2018 at 12:32:48PM +0900, Masahiro Yamada wrote: > > > > How about clang? > > > > For clang, -Og might be equivalent to -O1 at t

Re: linux-next: Tree for Oct 31 (vboxguest)

2018-11-02 Thread Changbin Du
On Fri, Nov 02, 2018 at 04:54:25PM +0100, Arnd Bergmann wrote: > On 11/2/18, Masahiro Yamada wrote: > > On Thu, Nov 1, 2018 at 11:32 PM Changbin Du wrote: > >> On Thu, Nov 01, 2018 at 12:32:48PM +0900, Masahiro Yamada wrote: > > > > How about clang? > > > > For clang, -Og might be equivalent to -

Re: linux-next: Tree for Oct 31 (vboxguest)

2018-11-02 Thread Changbin Du
Hi Yamada, >On Fri, Nov 02, 2018 at 05:25:00PM +0900, Masahiro Yamada wrote: >[...] > > > > > > > > diff --git a/drivers/virt/vboxguest/vboxguest_core.c > > > > b/drivers/virt/vboxguest/vboxguest_core.c > > > > index 3093655c7b92..1475ed5ffcde 100644 > > > > --- a/drivers/virt/vboxguest/vboxguest_c

Re: linux-next: Tree for Oct 31 (vboxguest)

2018-11-02 Thread Arnd Bergmann
On 11/2/18, Masahiro Yamada wrote: > On Thu, Nov 1, 2018 at 11:32 PM Changbin Du wrote: >> On Thu, Nov 01, 2018 at 12:32:48PM +0900, Masahiro Yamada wrote: > > How about clang? > > For clang, -Og might be equivalent to -O1 at this moment, but I am not > sure. > > In my understanding, Clang does n

Re: linux-next: Tree for Oct 31 (vboxguest)

2018-11-02 Thread Masahiro Yamada
On Thu, Nov 1, 2018 at 11:32 PM Changbin Du wrote: > > On Thu, Nov 01, 2018 at 12:32:48PM +0900, Masahiro Yamada wrote: > > Hi Arnd, > > > > > > On Thu, Nov 1, 2018 at 6:42 AM Arnd Bergmann wrote: > > > > > > On 10/31/18, Randy Dunlap wrote: > > > > On 10/30/18 8:59 PM, Stephen Rothwell wrote: >

Re: linux-next: Tree for Oct 31 (vboxguest)

2018-11-01 Thread Changbin Du
On Thu, Nov 01, 2018 at 12:32:48PM +0900, Masahiro Yamada wrote: > Hi Arnd, > > > On Thu, Nov 1, 2018 at 6:42 AM Arnd Bergmann wrote: > > > > On 10/31/18, Randy Dunlap wrote: > > > On 10/30/18 8:59 PM, Stephen Rothwell wrote: > > >> Hi all, > > >> > > >> Please do not add any v4.21/v5.1 code to

Re: linux-next: Tree for Oct 31 (vboxguest)

2018-10-31 Thread Masahiro Yamada
Hi Arnd, On Thu, Nov 1, 2018 at 6:42 AM Arnd Bergmann wrote: > > On 10/31/18, Randy Dunlap wrote: > > On 10/30/18 8:59 PM, Stephen Rothwell wrote: > >> Hi all, > >> > >> Please do not add any v4.21/v5.1 code to your linux-next included trees > >> until after the merge window closes. > >> > >> C

Re: linux-next: Tree for Oct 31 (vboxguest)

2018-10-31 Thread Randy Dunlap
On 10/31/18 2:41 PM, Arnd Bergmann wrote: > On 10/31/18, Randy Dunlap wrote: >> On 10/30/18 8:59 PM, Stephen Rothwell wrote: >>> Hi all, >>> >>> Please do not add any v4.21/v5.1 code to your linux-next included trees >>> until after the merge window closes. >>> >>> Changes since 20181030: >>> >> >

Re: linux-next: Tree for Oct 31 (vboxguest)

2018-10-31 Thread Arnd Bergmann
On 10/31/18, Randy Dunlap wrote: > On 10/30/18 8:59 PM, Stephen Rothwell wrote: >> Hi all, >> >> Please do not add any v4.21/v5.1 code to your linux-next included trees >> until after the merge window closes. >> >> Changes since 20181030: >> > > > on i386: > > ld: drivers/virt/vboxguest/vboxguest_

Re: linux-next: Tree for Oct 31 (vboxguest)

2018-10-31 Thread Randy Dunlap
On 10/31/18 9:50 AM, Hans de Goede wrote: > Hi, > > On 31-10-18 16:51, Randy Dunlap wrote: >> On 10/30/18 8:59 PM, Stephen Rothwell wrote: >>> Hi all, >>> >>> Please do not add any v4.21/v5.1 code to your linux-next included trees >>> until after the merge window closes. >>> >>> Changes since 2018

Re: linux-next: Tree for Oct 31 (vboxguest)

2018-10-31 Thread Hans de Goede
Hi, On 31-10-18 16:51, Randy Dunlap wrote: On 10/30/18 8:59 PM, Stephen Rothwell wrote: Hi all, Please do not add any v4.21/v5.1 code to your linux-next included trees until after the merge window closes. Changes since 20181030: on i386: ld: drivers/virt/vboxguest/vboxguest_core.o: in fu

Re: linux-next: Tree for Oct 31 (vboxguest)

2018-10-31 Thread Randy Dunlap
On 10/30/18 8:59 PM, Stephen Rothwell wrote: > Hi all, > > Please do not add any v4.21/v5.1 code to your linux-next included trees > until after the merge window closes. > > Changes since 20181030: > on i386: ld: drivers/virt/vboxguest/vboxguest_core.o: in function `vbg_ioctl_hgcm_call': vbox

linux-next: Tree for Oct 31

2018-10-30 Thread Stephen Rothwell
Hi all, Please do not add any v4.21/v5.1 code to your linux-next included trees until after the merge window closes. Changes since 20181030: My fixes tree contains this: "drivers: net: include linux/ip.h for iphdr" The xfs tree gained a conflict against Linus' tree. The vfs tree gained a co

linux-next: Tree for Oct 31

2014-10-30 Thread Stephen Rothwell
Hi all, Changes since 20141030: The hid tree gained a conflict against Linus' tree. The akpm-current tree lost its build failure. Non-merge commits (relative to Linus' tree): 3051 2487 files changed, 79125 insertions(+), 103302 deletions(-)

Re: linux-next: Tree for Oct 31 (crypto, rsa, mpi)

2013-11-01 Thread Randy Dunlap
On 11/01/13 08:16, David Howells wrote: > Randy Dunlap wrote: > >> crypto/built-in.o: In function `RSA_verify_signature': >> rsa.c:(.text+0x1d347): undefined reference to `mpi_get_nbits' >> rsa.c:(.text+0x1d354): undefined reference to `mpi_get_nbits' >> ... > > Does the attached patch fix it fo

Re: linux-next: Tree for Oct 31 (crypto, rsa, mpi)

2013-11-01 Thread David Howells
Randy Dunlap wrote: > crypto/built-in.o: In function `RSA_verify_signature': > rsa.c:(.text+0x1d347): undefined reference to `mpi_get_nbits' > rsa.c:(.text+0x1d354): undefined reference to `mpi_get_nbits' > ... Does the attached patch fix it for you? David --- KEYS: The RSA public key algorith

Re: linux-next: Tree for Oct 31 (input & leds)

2013-10-31 Thread Randy Dunlap
On 10/31/13 18:21, Samuel Thibault wrote: > Randy Dunlap, le Thu 31 Oct 2013 11:04:59 -0700, a écrit : >> On 10/31/13 03:00, Stephen Rothwell wrote: >>> Hi all, >>> >>> Changes since 20131030: >>> >>> The net-next tree gained a conflict against the net tree. >>> >>> The devicetree tree gained a con

Re: linux-next: Tree for Oct 31 (input & leds)

2013-10-31 Thread Samuel Thibault
Randy Dunlap, le Thu 31 Oct 2013 11:04:59 -0700, a écrit : > On 10/31/13 03:00, Stephen Rothwell wrote: > > Hi all, > > > > Changes since 20131030: > > > > The net-next tree gained a conflict against the net tree. > > > > The devicetree tree gained a conflict against the crypto tree. > > > > Th

Re: linux-next: Tree for Oct 31 (crypto, rsa, mpi)

2013-10-31 Thread Randy Dunlap
On 10/31/13 03:00, Stephen Rothwell wrote: > Hi all, > > Changes since 20131030: > > The net-next tree gained a conflict against the net tree. > > The devicetree tree gained a conflict against the crypto tree. > > The tty tree gained a build failure so I used the version from > next-20131030. >

linux-next: Tree for Oct 31

2013-10-31 Thread Stephen Rothwell
Hi all, Changes since 20131030: The net-next tree gained a conflict against the net tree. The devicetree tree gained a conflict against the crypto tree. The tty tree gained a build failure so I used the version from next-20131030. The arm-soc tree gained conflicts against the devicetree tree.

Re: linux-next: Tree for Oct 31 (ehci, dbgp)

2012-11-02 Thread Greg KH
On Fri, Nov 02, 2012 at 10:20:27AM -0400, Alan Stern wrote: > On Fri, 2 Nov 2012, Jan Beulich wrote: > > > >>> On 02.11.12 at 15:01, Alan Stern wrote: > > > On Thu, 1 Nov 2012, Jan Beulich wrote: > > > > > >> >>> Alan Stern 11/01/12 9:39 PM >>> > > >> >On Thu, 1 Nov 2012, Jan Beulich wrote: > >

Re: linux-next: Tree for Oct 31 (ehci, dbgp)

2012-11-02 Thread Alan Stern
On Fri, 2 Nov 2012, Jan Beulich wrote: > >>> On 02.11.12 at 15:01, Alan Stern wrote: > > On Thu, 1 Nov 2012, Jan Beulich wrote: > > > >> >>> Alan Stern 11/01/12 9:39 PM >>> > >> >On Thu, 1 Nov 2012, Jan Beulich wrote: > >> >> >>> Alan Stern 11/01/12 4:28 PM >>> > >> >> >Evidently we need to ch

Re: linux-next: Tree for Oct 31 (ehci, dbgp)

2012-11-02 Thread Jan Beulich
>>> On 02.11.12 at 15:01, Alan Stern wrote: > On Thu, 1 Nov 2012, Jan Beulich wrote: > >> >>> Alan Stern 11/01/12 9:39 PM >>> >> >On Thu, 1 Nov 2012, Jan Beulich wrote: >> >> >>> Alan Stern 11/01/12 4:28 PM >>> >> >> >Evidently we need to change your new test in >> >> >drivers/usb/early/ehci-db

Re: linux-next: Tree for Oct 31 (ehci, dbgp)

2012-11-02 Thread Alan Stern
On Thu, 1 Nov 2012, Jan Beulich wrote: > >>> Alan Stern 11/01/12 9:39 PM >>> > >On Thu, 1 Nov 2012, Jan Beulich wrote: > >> >>> Alan Stern 11/01/12 4:28 PM >>> > >> >Evidently we need to change your new test in > >> >drivers/usb/early/ehci-dbgp.c to: > >> > > >> >#if IS_ENABLED(CONFIG_USB_HCD_EH

Re: linux-next: Tree for Oct 31 (ehci, dbgp)

2012-11-01 Thread Jan Beulich
>>> Alan Stern 11/01/12 9:39 PM >>> >On Thu, 1 Nov 2012, Jan Beulich wrote: >> >>> Alan Stern 11/01/12 4:28 PM >>> >> >Evidently we need to change your new test in >> >drivers/usb/early/ehci-dbgp.c to: >> > >> >#if IS_ENABLED(CONFIG_USB_HCD_EHCI) || defined(CONFIG_USB_CHIPIDEA_HOST) >> > >> >Upco

Re: linux-next: Tree for Oct 31 (ehci, dbgp)

2012-11-01 Thread Alan Stern
On Thu, 1 Nov 2012, Jan Beulich wrote: > >>> Alan Stern 11/01/12 4:28 PM >>> > >On Wed, 31 Oct 2012, Randy Dunlap wrote: > >> on x86_64: > >> > >> drivers/built-in.o: In function `ehci_reset': > >> host.c:(.text+0x542a7e): undefined reference to `dbgp_reset_prep' > >> host.c:(.text+0x542b75): un

Re: linux-next: Tree for Oct 31 (ehci, dbgp)

2012-11-01 Thread Jan Beulich
>>> Alan Stern 11/01/12 4:28 PM >>> >On Wed, 31 Oct 2012, Randy Dunlap wrote: >> on x86_64: >> >> drivers/built-in.o: In function `ehci_reset': >> host.c:(.text+0x542a7e): undefined reference to `dbgp_reset_prep' >> host.c:(.text+0x542b75): undefined reference to `dbgp_external_startup' >> driver

Re: linux-next: Tree for Oct 31 (ehci, dbgp)

2012-11-01 Thread Alan Stern
On Wed, 31 Oct 2012, Randy Dunlap wrote: > On 10/30/2012 11:26 PM, Stephen Rothwell wrote: > > > Hi all, > > > > Changes since 20121030: > > > > > on x86_64: > > drivers/built-in.o: In function `ehci_reset': > host.c:(.text+0x542a7e): undefined reference to `dbgp_reset_prep' > host.c:(.text+

linux-next: Tree for Oct 31

2012-10-30 Thread Stephen Rothwell
Hi all, Changes since 20121030: The v4l-dvb tree still had its build failure so I used the version from next-20121026. The block tree gained a conflict against Linus' tree. The arm-soc tree gained a conflict against the staging tree.