Re: linux-next: Tree for Nov 4 (drivers/regulator/qcom-rpmh-regulator.o)

2020-11-04 Thread Randy Dunlap
On 11/3/20 10:01 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20201103: > on x86_64: CONFIG_QCOM_RPMH=m CONFIG_REGULATOR_QCOM_RPMH=y ld: drivers/regulator/qcom-rpmh-regulator.o: in function `rpmh_regulator_send_request': qcom-rpmh-regulator.c:(.text+0x106): undefined reference to

linux-next: Tree for Nov 4

2020-11-03 Thread Stephen Rothwell
Hi all, Changes since 20201103: The drm-intel-fixes tree gained a build failure for which I reverted a commit. The imx-mxs tree lost its build failure. The f2fs tree lost its build failure. The net-next tree gained a conflict against the net tree. The pinctrl tree still had its build

Re: linux-next: Tree for Nov 4 (serial console & earlycon)

2015-11-04 Thread Peter Hurley
On 11/04/2015 01:43 PM, Randy Dunlap wrote: > On 11/03/15 22:38, Stephen Rothwell wrote: >> Hi all, >> >> Please do *not* add any material intended for v4.5 to your linux-next >> included branches until after v4.4-rc1 has been released. >> >> Changes since 20151103: >> > > > on x86_64: > >

Re: linux-next: Tree for Nov 4 (serial console & earlycon)

2015-11-04 Thread Randy Dunlap
On 11/03/15 22:38, Stephen Rothwell wrote: > Hi all, > > Please do *not* add any material intended for v4.5 to your linux-next > included branches until after v4.4-rc1 has been released. > > Changes since 20151103: > on x86_64: drivers/built-in.o: In function `setup_earlycon':

Re: linux-next: Tree for Nov 4 (serial console & earlycon)

2015-11-04 Thread Peter Hurley
On 11/04/2015 01:43 PM, Randy Dunlap wrote: > On 11/03/15 22:38, Stephen Rothwell wrote: >> Hi all, >> >> Please do *not* add any material intended for v4.5 to your linux-next >> included branches until after v4.4-rc1 has been released. >> >> Changes since 20151103: >> > > > on x86_64: > >

Re: linux-next: Tree for Nov 4 (serial console & earlycon)

2015-11-04 Thread Randy Dunlap
On 11/03/15 22:38, Stephen Rothwell wrote: > Hi all, > > Please do *not* add any material intended for v4.5 to your linux-next > included branches until after v4.4-rc1 has been released. > > Changes since 20151103: > on x86_64: drivers/built-in.o: In function `setup_earlycon':

linux-next: Tree for Nov 4

2015-11-03 Thread Stephen Rothwell
Hi all, Please do *not* add any material intended for v4.5 to your linux-next included branches until after v4.4-rc1 has been released. Changes since 20151103: The battery tree still had its build failure so I used the version from next-20150925. The mailbox tree still had its build failure so

linux-next: Tree for Nov 4

2015-11-03 Thread Stephen Rothwell
Hi all, Please do *not* add any material intended for v4.5 to your linux-next included branches until after v4.4-rc1 has been released. Changes since 20151103: The battery tree still had its build failure so I used the version from next-20150925. The mailbox tree still had its build failure so

Re: linux-next: Tree for Nov 4

2014-11-04 Thread Michael Ellerman
On Tue, 2014-11-04 at 22:56 +0100, Geert Uytterhoeven wrote: > Hi Stephen, Michael, > > On Tue, Nov 4, 2014 at 7:36 AM, Stephen Rothwell > wrote: > > Status of my local build tests will be at > > http://kisskb.ellerman.id.au/linux-next . If maintainers want to give > > advice about cross

Re: linux-next: Tree for Nov 4

2014-11-04 Thread Geert Uytterhoeven
Hi Stephen, Michael, On Tue, Nov 4, 2014 at 7:36 AM, Stephen Rothwell wrote: > Status of my local build tests will be at > http://kisskb.ellerman.id.au/linux-next . If maintainers want to give > advice about cross compilers/configs that work, we are always open to add > more builds. Looks like

Re: linux-next: Tree for Nov 4

2014-11-04 Thread Guenter Roeck
On Tue, Nov 04, 2014 at 05:36:24PM +1100, Stephen Rothwell wrote: > Hi all, > > Changes since 20141103: > > The mfd tree gained a build failure for which I reverted a commit. > > The scsi tree lost its build failure, but gained another so I used the > version from next-20141031. > > Non-merge

Re: linux-next: Tree for Nov 4

2014-11-04 Thread Guenter Roeck
On Tue, Nov 04, 2014 at 05:36:24PM +1100, Stephen Rothwell wrote: Hi all, Changes since 20141103: The mfd tree gained a build failure for which I reverted a commit. The scsi tree lost its build failure, but gained another so I used the version from next-20141031. Non-merge commits

Re: linux-next: Tree for Nov 4

2014-11-04 Thread Geert Uytterhoeven
Hi Stephen, Michael, On Tue, Nov 4, 2014 at 7:36 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . If maintainers want to give advice about cross compilers/configs that work, we are always open to add more

Re: linux-next: Tree for Nov 4

2014-11-04 Thread Michael Ellerman
On Tue, 2014-11-04 at 22:56 +0100, Geert Uytterhoeven wrote: Hi Stephen, Michael, On Tue, Nov 4, 2014 at 7:36 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . If maintainers want to give advice about

linux-next: Tree for Nov 4

2014-11-03 Thread Stephen Rothwell
Hi all, Changes since 20141103: The mfd tree gained a build failure for which I reverted a commit. The scsi tree lost its build failure, but gained another so I used the version from next-20141031. Non-merge commits (relative to Linus' tree): 3170 2579 files changed, 83652 insertions(+),

linux-next: Tree for Nov 4

2014-11-03 Thread Stephen Rothwell
Hi all, Changes since 20141103: The mfd tree gained a build failure for which I reverted a commit. The scsi tree lost its build failure, but gained another so I used the version from next-20141031. Non-merge commits (relative to Linus' tree): 3170 2579 files changed, 83652 insertions(+),

linux-next: Tree for Nov 4

2013-11-03 Thread Stephen Rothwell
Hi all, Changes since 20131101: The squashfs tree lost its build failure. The sound-asoc tree gained a build failure for which I reverted a commit. The modules tree introduced a very large number of warnings so I used the version from next-20131101. The block tree still had its build failure

linux-next: Tree for Nov 4

2013-11-03 Thread Stephen Rothwell
Hi all, Changes since 20131101: The squashfs tree lost its build failure. The sound-asoc tree gained a build failure for which I reverted a commit. The modules tree introduced a very large number of warnings so I used the version from next-20131101. The block tree still had its build failure