From: "Ondřej Jirman" <megous@megous.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-bluetooth@vger.kernel.org,
Marcel Holtmann <marcel@holtmann.org>
Subject: Re: [bluetooth-next:master 12/14] ERROR: Input tree has errors, aborting (use -f to force output)
Date: Fri, 30 Aug 2019 16:47:41 +0200 [thread overview]
Message-ID: <20190830144741.mjasfgireoja34fs@core.my.home> (raw)
In-Reply-To: <201908302208.p3EUe75L%lkp@intel.com>
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
prev parent reply other threads:[~2019-08-30 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190830144741.mjasfgireoja34fs@core.my.home \
--to=megous@megous.com \
--cc=kbuild-all@01.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=lkp@intel.com \
--cc=marcel@holtmann.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox