Re: linux-next: Tree for Dec 7 (kallsyms failure)

2016-12-07 Thread Nicholas Piggin
On Thu, 8 Dec 2016 15:29:35 +1100 Stephen Rothwell wrote: > Hi all, > > On Wed, 7 Dec 2016 18:30:57 -0800 Randy Dunlap wrote: > > > > On 12/07/16 15:56, Stephen Rothwell wrote: > > > > > > On Wed, 7 Dec 2016 15:42:32 -0800 Randy Dunlap

Re: linux-next: Tree for Dec 7 (kallsyms failure)

2016-12-07 Thread Nicholas Piggin
On Thu, 8 Dec 2016 15:29:35 +1100 Stephen Rothwell wrote: > Hi all, > > On Wed, 7 Dec 2016 18:30:57 -0800 Randy Dunlap wrote: > > > > On 12/07/16 15:56, Stephen Rothwell wrote: > > > > > > On Wed, 7 Dec 2016 15:42:32 -0800 Randy Dunlap > > > wrote: > > >> > > >> I started seeing this

Re: linux-next: Tree for Dec 7 (kallsyms failure)

2016-12-07 Thread Stephen Rothwell
Hi all, On Wed, 7 Dec 2016 18:30:57 -0800 Randy Dunlap wrote: > > On 12/07/16 15:56, Stephen Rothwell wrote: > > > > On Wed, 7 Dec 2016 15:42:32 -0800 Randy Dunlap > > wrote: > >> > >> I started seeing this yesterday (2016-1206). > >> This is on

Re: linux-next: Tree for Dec 7 (kallsyms failure)

2016-12-07 Thread Stephen Rothwell
Hi all, On Wed, 7 Dec 2016 18:30:57 -0800 Randy Dunlap wrote: > > On 12/07/16 15:56, Stephen Rothwell wrote: > > > > On Wed, 7 Dec 2016 15:42:32 -0800 Randy Dunlap > > wrote: > >> > >> I started seeing this yesterday (2016-1206). > >> This is on x86_64. > >> > >> Anybody know about it? > >>

Re: linux-next: Tree for Dec 7 (kallsyms failure)

2016-12-07 Thread Randy Dunlap
On 12/07/16 15:56, Stephen Rothwell wrote: > Hi Randy, > > On Wed, 7 Dec 2016 15:42:32 -0800 Randy Dunlap wrote: >> >> I started seeing this yesterday (2016-1206). >> This is on x86_64. >> >> Anybody know about it? >> >> kallsyms failure: relative symbol value

Re: linux-next: Tree for Dec 7 (kallsyms failure)

2016-12-07 Thread Randy Dunlap
On 12/07/16 15:56, Stephen Rothwell wrote: > Hi Randy, > > On Wed, 7 Dec 2016 15:42:32 -0800 Randy Dunlap wrote: >> >> I started seeing this yesterday (2016-1206). >> This is on x86_64. >> >> Anybody know about it? >> >> kallsyms failure: relative symbol value 0x8100 out of range in

Re: linux-next: Tree for Dec 7 (kallsyms failure)

2016-12-07 Thread Stephen Rothwell
Hi Randy, On Wed, 7 Dec 2016 15:42:32 -0800 Randy Dunlap wrote: > > I started seeing this yesterday (2016-1206). > This is on x86_64. > > Anybody know about it? > > kallsyms failure: relative symbol value 0x8100 out of range in > relative mode I got a

Re: linux-next: Tree for Dec 7 (kallsyms failure)

2016-12-07 Thread Stephen Rothwell
Hi Randy, On Wed, 7 Dec 2016 15:42:32 -0800 Randy Dunlap wrote: > > I started seeing this yesterday (2016-1206). > This is on x86_64. > > Anybody know about it? > > kallsyms failure: relative symbol value 0x8100 out of range in > relative mode I got a similar failure starting a

Re: linux-next: Tree for Dec 7 (kallsyms failure)

2016-12-07 Thread Randy Dunlap
On 12/06/16 22:24, Stephen Rothwell wrote: > Hi all, > > Changes since 20161206: > > The powerpc allyesconfig build fails for this release. > > The pinctrl tree still had its build failure so I used the version from > next-20161202. > > The sound-asoc tree lost its build failure. > > The tip

Re: linux-next: Tree for Dec 7 (kallsyms failure)

2016-12-07 Thread Randy Dunlap
On 12/06/16 22:24, Stephen Rothwell wrote: > Hi all, > > Changes since 20161206: > > The powerpc allyesconfig build fails for this release. > > The pinctrl tree still had its build failure so I used the version from > next-20161202. > > The sound-asoc tree lost its build failure. > > The tip