linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [bluetooth-next:master 12/14] ERROR: Input tree has errors, aborting (use -f to force output)
@ 2019-08-30 14:06 kbuild test robot
  2019-08-30 14:47 ` Ondřej Jirman
  0 siblings, 1 reply; 2+ messages in thread
From: kbuild test robot @ 2019-08-30 14:06 UTC (permalink / raw)
  To: Ondrej Jirman; +Cc: kbuild-all, linux-bluetooth, Marcel Holtmann

[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]

tree:   https://kernel.googlesource.com/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
head:   48108451ade420704f75cc4ffb57d5f5255b8dd8
commit: 15f6eb5351a2487b47c2c53e8e0569aaf1e3d56e [12/14] arm64: dts: allwinner: orange-pi-3: Enable UART1 / Bluetooth
config: arm64-defconfig (attached as .config)
compiler: aarch64-linux-gcc (GCC) 7.4.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        git checkout 15f6eb5351a2487b47c2c53e8e0569aaf1e3d56e
        # save the attached .config to linux build tree
        GCC_VERSION=7.4.0 make.cross ARCH=arm64 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

>> ERROR: Input tree has errors, aborting (use -f to force output)

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 45365 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [bluetooth-next:master 12/14] ERROR: Input tree has errors, aborting (use -f to force output)
  2019-08-30 14:06 [bluetooth-next:master 12/14] ERROR: Input tree has errors, aborting (use -f to force output) kbuild test robot
@ 2019-08-30 14:47 ` Ondřej Jirman
  0 siblings, 0 replies; 2+ messages in thread
From: Ondřej Jirman @ 2019-08-30 14:47 UTC (permalink / raw)
  To: kbuild test robot; +Cc: kbuild-all, linux-bluetooth, Marcel Holtmann

Hello,

On Fri, Aug 30, 2019 at 10:06:10PM +0800, kbuild test robot wrote:
> tree:   https://kernel.googlesource.com/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
> head:   48108451ade420704f75cc4ffb57d5f5255b8dd8
> commit: 15f6eb5351a2487b47c2c53e8e0569aaf1e3d56e [12/14] arm64: dts: allwinner: orange-pi-3: Enable UART1 / Bluetooth
> config: arm64-defconfig (attached as .config)
> compiler: aarch64-linux-gcc (GCC) 7.4.0
> reproduce:
>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         git checkout 15f6eb5351a2487b47c2c53e8e0569aaf1e3d56e
>         # save the attached .config to linux build tree
>         GCC_VERSION=7.4.0 make.cross ARCH=arm64 
> 
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
> 
> All errors (new ones prefixed by >>):
> 
> >> ERROR: Input tree has errors, aborting (use -f to force output)

Not a very helpful message, but googling this, it seems that this is
possibly a DTS issue? It should be fixed after reverting DTS changes
and applying them via the sunxi tree.

Sorry for the mess, I forgot to mention that DTS changes should go
via the sunxi tree. My bad.

thank you and regards,
	Ondrej

> ---
> 0-DAY kernel test infrastructure                Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all                   Intel Corporation



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2019-08-30 14:47 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-08-30 14:06 [bluetooth-next:master 12/14] ERROR: Input tree has errors, aborting (use -f to force output) kbuild test robot
2019-08-30 14:47 ` Ondřej Jirman

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).