linux-next: Tree for Nov 1

2018-10-31 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 20181031: My fixes tree contains this: "drivers: net: include linux/ip.h for iphdr" Non-merge commits (relative to Linus' tree): 790 953 files changed, 41712 in

Re: linux-next: Tree for Nov 1 (lightnvm)

2015-11-03 Thread Jens Axboe
On 11/02/2015 03:34 PM, Matias Bjorling wrote: On 11/02/2015 04:37 PM, Jens Axboe wrote: On 11/02/2015 05:43 AM, Matias Bjorling wrote: On 11/02/2015 02:16 AM, Randy Dunlap wrote: On 11/01/15 08:53, Stephen Rothwell wrote: Hi all, I start again a day early, and this is how you all repay me?

Re: linux-next: Tree for Nov 1 (lightnvm)

2015-11-02 Thread Matias Bjorling
On 11/02/2015 04:37 PM, Jens Axboe wrote: > On 11/02/2015 05:43 AM, Matias Bjorling wrote: >> On 11/02/2015 02:16 AM, Randy Dunlap wrote: >>> On 11/01/15 08:53, Stephen Rothwell wrote: Hi all, I start again a day early, and this is how you all repay me? ;-) Changes since 20

Re: linux-next: Tree for Nov 1 (xconfig problem)

2015-11-02 Thread Michal Marek
Dne 2.11.2015 v 20:23 Thiago Macieira napsal(a): > On Monday 02 November 2015 10:48:00 Randy Dunlap wrote: >> Hi, >> What does this patch apply to? >> I can't apply it cleanly to to 4.3 or linux-next of yesterday or today. > > Hmm... interesting, it doesn't apply on linux-next. The reason for that

Re: linux-next: Tree for Nov 1 (xconfig problem)

2015-11-02 Thread Thiago Macieira
On Monday 02 November 2015 10:48:00 Randy Dunlap wrote: > Hi, > What does this patch apply to? > I can't apply it cleanly to to 4.3 or linux-next of yesterday or today. Hmm... interesting, it doesn't apply on linux-next. The reason for that is that the code on linux-next is different from the one

Re: linux-next: Tree for Nov 1 (xconfig problem)

2015-11-02 Thread Randy Dunlap
On 11/02/15 08:58, Thiago Macieira wrote: > On Monday 02 November 2015 08:44:01 Randy Dunlap wrote: >>> Randy, we need a backtrace. The problem is on the function that called >>> first(). Can you make sure the crash generates a core dump, then get the >>> bt >>> from that? >> >> ASSERT: "!isEmpty()

Re: linux-next: Tree for Nov 1 (xconfig problem)

2015-11-02 Thread Thiago Macieira
On Monday 02 November 2015 08:44:01 Randy Dunlap wrote: > > Randy, we need a backtrace. The problem is on the function that called > > first(). Can you make sure the crash generates a core dump, then get the > > bt > > from that? > > ASSERT: "!isEmpty()" in file /usr/include/QtCore/qlist.h, line 2

Re: linux-next: Tree for Nov 1 (xconfig problem)

2015-11-02 Thread Randy Dunlap
On 11/02/15 05:51, Thiago Macieira wrote: > On Monday 02 November 2015 14:39:16 Michal Marek wrote: >> On 2015-11-02 04:11, Randy Dunlap wrote: >>> On 11/01/15 08:53, Stephen Rothwell wrote: Hi all, I start again a day early, and this is how you all repay me? ;-) >>> Changes sin

Re: linux-next: Tree for Nov 1 (xconfig problem)

2015-11-02 Thread Randy Dunlap
On 11/02/15 05:39, Michal Marek wrote: > On 2015-11-02 04:11, Randy Dunlap wrote: >> On 11/01/15 08:53, Stephen Rothwell wrote: >>> Hi all, >>> >>> I start again a day early, and this is how you all repay me? ;-) >>> >>> Changes since 20151022: >>> >> >> on x86_64: >> >> 'make xconfig' dies a quick

Re: linux-next: Tree for Nov 1 (lightnvm)

2015-11-02 Thread Jens Axboe
On 11/02/2015 05:43 AM, Matias Bjorling wrote: On 11/02/2015 02:16 AM, Randy Dunlap wrote: On 11/01/15 08:53, Stephen Rothwell wrote: Hi all, I start again a day early, and this is how you all repay me? ;-) Changes since 20151022: on i386: ../include/linux/lightnvm.h:143:4: error: width o

Re: linux-next: Tree for Nov 1 (xconfig problem)

2015-11-02 Thread Thiago Macieira
On Monday 02 November 2015 14:39:16 Michal Marek wrote: > On 2015-11-02 04:11, Randy Dunlap wrote: > > On 11/01/15 08:53, Stephen Rothwell wrote: > >> Hi all, > >> > >> I start again a day early, and this is how you all repay me? ;-) > > > >> Changes since 20151022: > > on x86_64: > > > > 'make

Re: linux-next: Tree for Nov 1 (xconfig problem)

2015-11-02 Thread Michal Marek
On 2015-11-02 04:11, Randy Dunlap wrote: > On 11/01/15 08:53, Stephen Rothwell wrote: >> Hi all, >> >> I start again a day early, and this is how you all repay me? ;-) >> >> Changes since 20151022: >> > > on x86_64: > > 'make xconfig' dies a quick death when I try to use it: > > linux-next-20151

Re: linux-next: Tree for Nov 1 (lightnvm)

2015-11-02 Thread Matias Bjorling
On 11/02/2015 02:16 AM, Randy Dunlap wrote: > On 11/01/15 08:53, Stephen Rothwell wrote: >> Hi all, >> >> I start again a day early, and this is how you all repay me? ;-) >> >> Changes since 20151022: >> > > on i386: > > ../include/linux/lightnvm.h:143:4: error: width of 'resved' exceeds its type

Re: linux-next: Tree for Nov 1

2015-11-02 Thread Geert Uytterhoeven
Hi Stephen, On Sun, Nov 1, 2015 at 5:53 PM, Stephen Rothwell wrote: > I start again a day early, and this is how you all repay me? ;-) With all these maintainers showing you fake smiles at Kernel Summit :-) This only proves how much value your work brings! Thanks a lot! If I have to answer the

Re: linux-next: Tree for Nov 1 (xconfig problem)

2015-11-01 Thread Randy Dunlap
On 11/01/15 08:53, Stephen Rothwell wrote: > Hi all, > > I start again a day early, and this is how you all repay me? ;-) > > Changes since 20151022: > on x86_64: 'make xconfig' dies a quick death when I try to use it: linux-next-20151101> ASSERT: "!isEmpty()" in file /usr/include/QtCore/qlis

Re: linux-next: Tree for Nov 1 (lightnvm)

2015-11-01 Thread Randy Dunlap
On 11/01/15 08:53, Stephen Rothwell wrote: > Hi all, > > I start again a day early, and this is how you all repay me? ;-) > > Changes since 20151022: > on i386: ../include/linux/lightnvm.h:143:4: error: width of 'resved' exceeds its type # CONFIG_LBDAF is not set -- ~Randy -- To unsubscrib

linux-next: Tree for Nov 1

2015-11-01 Thread Stephen Rothwell
Hi all, I start again a day early, and this is how you all repay me? ;-) Changes since 20151022: New trees: usb-chipidea-fixes, usb-chipidea-next Removed tree: kdbus (temporarily at the maintainer's request) The mvebu tree gained a conflict against the arm-soc tree. The arm64 tree gained a co

Re: linux-next: Tree for Nov 1 (xen_swiotllb)

2013-11-04 Thread Stefano Stabellini
On Fri, 1 Nov 2013, Konrad Rzeszutek Wilk wrote: > On Fri, Nov 01, 2013 at 11:16:26AM -0700, Randy Dunlap wrote: > > On 11/01/13 01:11, Stephen Rothwell wrote: > > > Hi all, > > > > > > Changes since 20131031: > > > > > > The squashfs tree gained a build failure so I used the version from > > > n

Re: linux-next: Tree for Nov 1 (xen_swiotllb)

2013-11-04 Thread Konrad Rzeszutek Wilk
On Mon, Nov 04, 2013 at 06:20:42PM +, Stefano Stabellini wrote: > On Fri, 1 Nov 2013, Konrad Rzeszutek Wilk wrote: > > On Fri, Nov 01, 2013 at 11:16:26AM -0700, Randy Dunlap wrote: > > > On 11/01/13 01:11, Stephen Rothwell wrote: > > > > Hi all, > > > > > > > > Changes since 20131031: > > > >

Re: linux-next: Tree for Nov 1 (xen_swiotllb)

2013-11-01 Thread Konrad Rzeszutek Wilk
On Fri, Nov 01, 2013 at 11:16:26AM -0700, Randy Dunlap wrote: > On 11/01/13 01:11, Stephen Rothwell wrote: > > Hi all, > > > > Changes since 20131031: > > > > The squashfs tree gained a build failure so I used the version from > > next-20131031. > > > > The block tree gained conflicts against th

Re: linux-next: Tree for Nov 1 (xen_swiotllb)

2013-11-01 Thread Randy Dunlap
On 11/01/13 01:11, Stephen Rothwell wrote: > Hi all, > > Changes since 20131031: > > The squashfs tree gained a build failure so I used the version from > next-20131031. > > The block tree gained conflicts against the f2fs, aio-direct and Linus' > trees and a build failure and generated several

linux-next: Tree for Nov 1

2013-11-01 Thread Stephen Rothwell
Hi all, Changes since 20131031: The squashfs tree gained a build failure so I used the version from next-20131031. The block tree gained conflicts against the f2fs, aio-direct and Linus' trees and a build failure and generated several warnings so I used the version from next-20131031. The dt-rh

Re: linux-next: Tree for Nov 1 (xen)

2012-11-01 Thread Konrad Rzeszutek Wilk
On Thu, Nov 01, 2012 at 10:18:47AM -0700, Randy Dunlap wrote: > On 10/31/2012 10:36 PM, Stephen Rothwell wrote: > > > Hi all, > > > > New trees: rr-fixes and swiotlb > > > > Changes since 20121031: > > > > > arch/x86/xen/enlighten.c:109:0: warning: "xen_pvh_domain" redefined > include/xen/xen

Re: linux-next: Tree for Nov 1 (xen)

2012-11-01 Thread Randy Dunlap
On 10/31/2012 10:36 PM, Stephen Rothwell wrote: > Hi all, > > New trees: rr-fixes and swiotlb > > Changes since 20121031: > arch/x86/xen/enlighten.c:109:0: warning: "xen_pvh_domain" redefined include/xen/xen.h:23:0: note: this is the location of the previous definition Full randconfig file i

linux-next: Tree for Nov 1

2012-10-31 Thread Stephen Rothwell
Hi all, New trees: rr-fixes and swiotlb Changes since 20121031: The v4l-dvb tree still had its build failure so I used the version from next-20121026. The tmem tree gained conflicts against the xen-two tree. The akpm tree lost a patch that turned up elsewhere.