All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Build bot for Mark Brown <broonie@kernel.org>
Cc: kernel-build-reports@lists.linaro.org,
	linaro-kernel@lists.linaro.org, stable@vger.kernel.org
Subject: Re: v3.10.105 build: 1 failures 174 warnings (v3.10.105)
Date: Mon, 27 Mar 2017 14:21:46 +0200	[thread overview]
Message-ID: <20170327122146.GB25373@1wt.eu> (raw)
In-Reply-To: <E1csSoH-0004j8-FQ@optimist>

On Mon, Mar 27, 2017 at 12:27:41PM +0100, Build bot for Mark Brown wrote:
> Tree/Branch: v3.10.105
> Git describe: v3.10.105
> Commit: ec55e7c2bf Linux 3.10.105
> 
> Build Time: 19 min 21 sec
> 
> Passed:    7 / 8   ( 87.50 %)
> Failed:    1 / 8   ( 12.50 %)
> 
> Errors: 1
> Warnings: 174
> Section Mismatches: 0
> 
> Failed defconfigs:
> 	arm64-allmodconfig
> 
> Errors:
> 
> 	arm64-allmodconfig
> /home/broonie/build/linux-stable/include/linux/module.h:87:32: error: storage size of '__mod_amba_device_table' isn't known
> /home/broonie/build/linux-stable/include/linux/module.h:87:32: error: storage size of '__mod_amba_device_table' isn't known
> /home/broonie/build/linux-stable/include/linux/module.h:87:32: error: storage size of '__mod_amba_device_table' isn't known
> /home/broonie/build/linux-stable/include/linux/module.h:87:32: error: storage size of '__mod_amba_device_table' isn't known
> /home/broonie/build/linux-stable/include/linux/module.h:87:32: error: storage size of '__mod_amba_device_table' isn't known
> /home/broonie/build/linux-stable/include/linux/module.h:87:32: error: storage size of '__mod_amba_device_table' isn't known
> /home/broonie/build/linux-stable/include/linux/module.h:87:32: error: storage size of '__mod_amba_device_table' isn't known
> /home/broonie/build/linux-stable/include/linux/module.h:87:32: error: storage size of '__mod_amba_device_table' isn't known
> /home/broonie/build/linux-stable/include/linux/module.h:87:32: error: storage size of '__mod_amba_device_table' isn't known

Interesting, nothing seems to have changed regrading this between
3.10.104 and 3.10.105 so it's possible the issue is in fact older.
I do have an arm64 toolchain here, I'll try to figure what the problem
is.

Thanks,
Willy

  reply	other threads:[~2017-03-27 12:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27 11:27 v3.10.105 build: 1 failures 174 warnings (v3.10.105) Build bot for Mark Brown
2017-03-27 12:21 ` Willy Tarreau [this message]
2017-03-27 14:30   ` Mark Brown
2017-03-27 14:35     ` Arnd Bergmann
2017-03-27 14:40       ` Mark Brown
2017-03-28  7:28   ` Arnd Bergmann
2017-03-28  7:29     ` Arnd Bergmann

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=20170327122146.GB25373@1wt.eu \
    --to=w@1wt.eu \
    --cc=broonie@kernel.org \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.