Skip to contentSkip to conversation

next-20170815 build: 2 failures 4 warnings (next-20170815)

DISCUSSION Build bot for Mark Brown 4 participants 5 messages Aug 15, 2017 – Aug 16, 2017

Subsystems (2)
lore
Share & tools
lore
author maintainer
#1 lore raw
In reply to Build bot for Mark Brown

On Tue, Aug 15, 2017 at 11:49:36AM +0100, Build bot for Mark Brown wrote:

Today's -next fails to build on arm64 due to:

Quoted 4 lines

arm64-allmodconfig
arm64-defconfig
../drivers/acpi/spcr.c:168:1: error: expected expression before '<<' token ../drivers/acpi/spcr.c:198:1: error: expected expression before '>>' token

caused by f69ba1326ac33b (Merge branch 'acpi-spcr' into linux-next)
which has an unresolved conflict in it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170815/2be35cf6/attachment.sig>

Build bot for Mark Brown

author maintainer
#0 lore raw

Tree/Branch: next-20170815
Git describe: next-20170815
Commit: 497247033e Add linux-next specific files for 20170815

Build Time: 78 min 48 sec

Passed:    8 / 10   ( 80.00 %)
Failed:    2 / 10   ( 20.00 %)

Errors: 2
Warnings: 4
Section Mismatches: 0

Failed defconfigs:
arm64-allmodconfig
arm64-defconfig

Errors:

arm64-allmodconfig
../drivers/acpi/spcr.c:168:1: error: expected expression before '<<' token ../drivers/acpi/spcr.c:198:1: error: expected expression before '>>' token

arm64-defconfig
../drivers/acpi/spcr.c:168:1: error: expected expression before '<<' token ../drivers/acpi/spcr.c:198:1: error: expected expression before '>>' token

-------------------------------------------------------------------------------
defconfigs with issues (other than build errors):

      1 warnings    0 mismatches  : x86_64-allnoconfig
      1 warnings    0 mismatches  : arm64-allmodconfig
      2 warnings    0 mismatches  : arm-allmodconfig
      1 warnings    0 mismatches  : arm64-defconfig

-------------------------------------------------------------------------------

Errors summary: 2
2 ../drivers/acpi/spcr.c:198:1: error: expected expression before '>>' token 2 ../drivers/acpi/spcr.c:168:1: error: expected expression before '<<' token

Warnings Summary: 4

	  2 ../drivers/acpi/spcr.c:34:13: warning: 'qdf2400_erratum_44_present' defined but not used [-Wunused-function]
	  1 ../drivers/mmc/core/mmc_test.c:883:1: warning: the frame size of 1032 bytes is larger than 1024 bytes [-Wframe-larger-than=]
	  1 ../drivers/md/dm-integrity.c:827:1: warning: the frame size of 1248 bytes is larger than 1024 bytes [-Wframe-larger-than=]
	  1 ../arch/x86/kernel/cpu/amd.c:305:13: warning: 'legacy_fixup_core_id' defined but not used [-Wunused-function]

===============================================================================
Detailed per-defconfig build reports below:

-------------------------------------------------------------------------------
x86_64-allnoconfig : PASS, 0 errors, 1 warnings, 0 section mismatches

Warnings:

	../arch/x86/kernel/cpu/amd.c:305:13: warning: 'legacy_fixup_core_id' defined but not used [-Wunused-function]

-------------------------------------------------------------------------------
arm64-allmodconfig : FAIL, 2 errors, 1 warnings, 0 section mismatches

Errors:
../drivers/acpi/spcr.c:168:1: error: expected expression before '<<' token ../drivers/acpi/spcr.c:198:1: error: expected expression before '>>' token

Warnings:

	../drivers/acpi/spcr.c:34:13: warning: 'qdf2400_erratum_44_present' defined but not used [-Wunused-function]

-------------------------------------------------------------------------------
arm-allmodconfig : PASS, 0 errors, 2 warnings, 0 section mismatches

Warnings:
../drivers/md/dm-integrity.c:827:1: warning: the frame size of 1248 bytes is larger than 1024 bytes [-Wframe-larger-than=] ../drivers/mmc/core/mmc_test.c:883:1: warning: the frame size of 1032 bytes is larger than 1024 bytes [-Wframe-larger-than=]

-------------------------------------------------------------------------------
arm64-defconfig : FAIL, 2 errors, 1 warnings, 0 section mismatches

Errors:
../drivers/acpi/spcr.c:168:1: error: expected expression before '<<' token ../drivers/acpi/spcr.c:198:1: error: expected expression before '>>' token

Warnings:

	../drivers/acpi/spcr.c:34:13: warning: 'qdf2400_erratum_44_present' defined but not used [-Wunused-function]

-------------------------------------------------------------------------------

Passed with no errors, warnings or mismatches:

arm64-allnoconfig
arm-multi_v5_defconfig
arm-multi_v7_defconfig
x86_64-defconfig
arm-allnoconfig
arm-multi_v4t_defconfig

#2 lore raw
In reply to Mark Brown
Quoted 9 lines · CEST Mark Brown

--xqegarazqzvkdxmo
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Tue, Aug 15, 2017 at 11:49:36AM +0100, Build bot for Mark Brown wrote:

Today's -next fails to build on arm64 due to:

Quoted 7 lines
Quoted 4 lines

arm64-allmodconfig
arm64-defconfig
../drivers/acpi/spcr.c:168:1: error: expected expression before '<<' token ../drivers/acpi/spcr.c:198:1: error: expected expression before '>>' token

caused by f69ba1326ac33b (Merge branch 'acpi-spcr' into linux-next) which has an unresolved conflict in it.

Yes, I broke this, sorry.

Will fix it shortly.

Thanks,
Rafael

#3 lore raw

Hi Rafael,

Quoted 14 lines · Rafael J. Wysocki
Quoted 13 lines · CEST Mark Brown

--xqegarazqzvkdxmo
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Tue, Aug 15, 2017 at 11:49:36AM +0100, Build bot for Mark Brown wrote:

Today's -next fails to build on arm64 due to:

Quoted 4 lines

arm64-allmodconfig
arm64-defconfig
../drivers/acpi/spcr.c:168:1: error: expected expression before '<<' token ../drivers/acpi/spcr.c:198:1: error: expected expression before '>>' token

Quoted 6 lines
Quoted 2 lines

caused by f69ba1326ac33b (Merge branch 'acpi-spcr' into linux-next) which has an unresolved conflict in it.

Yes, I broke this, sorry.

Will fix it shortly.

The rebased version (fix?) lacks a curly opening brace. Gmail-whitespace-damaged patch to fold into the bad version below.

Quoted 1 line

From f5d55ccb53f02b67be52962d727bdfe3fff14afb Mon Sep 17 00:00:00 2001

From: Geert Uytterhoeven <[email protected]>
Date: Wed, 16 Aug 2017 15:17:35 +0200
Subject: [PATCH] CPI: SPCR: Add missing opening brace

drivers/acpi/spcr.c: In function 'parse_spcr':
drivers/acpi/spcr.c:165:3: error: label 'done' used but not defined
goto done;
^
drivers/acpi/spcr.c: At top level:
drivers/acpi/spcr.c:201:4: error: expected identifier or '(' before 'else'

  } else {
    ^
drivers/acpi/spcr.c:206:9: error: expected declaration specifiers or
'...' before string constant
  pr_info("console: %s\n", opts);
         ^
drivers/acpi/spcr.c:206:52: error: unknown type name 'opts'
  pr_info("console: %s\n", opts);
                                                    ^

drivers/acpi/spcr.c:208:2: error: expected identifier or '(' before 'if'
if (earlycon)
^
drivers/acpi/spcr.c:211:2: warning: data definition has no type or storage class
err = add_preferred_console(uart, 0, opts + strlen(uart) + 1);
^
drivers/acpi/spcr.c:211:2: error: type defaults to 'int' in declaration of 'err' [-Werror=implicit-int] drivers/acpi/spcr.c:211:30: error: 'uart' undeclared here (not in a function)

  err = add_preferred_console(uart, 0, opts + strlen(uart) + 1);
                              ^
drivers/acpi/spcr.c:211:39: error: 'opts' undeclared here (not in a function)
  err = add_preferred_console(uart, 0, opts + strlen(uart) + 1);
                                       ^
drivers/acpi/spcr.c:213:5: error: expected '=', ',', ';', 'asm' or
'__attribute__' before ':' token
 done:
     ^

drivers/acpi/spcr.c:215:2: error: expected identifier or '(' before 'return'
return err;
^
drivers/acpi/spcr.c:216:1: error: expected identifier or '(' before '}' token
}
^
drivers/acpi/spcr.c: In function 'parse_spcr':
drivers/acpi/spcr.c:201:2: warning: control reaches end of non-void function [-Wreturn-type]
} else {
^

Fixes fd46b1aebee729fb ("ACPI: SPCR: work around clock issue on xgene UART")
---
 drivers/acpi/spcr.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/acpi/spcr.c +1 -1
index 617003032415e09e..324b35bfe781d42a 100644
@@ -189,7 +189,7 @@ int __init parse_spcr(bool earlycon)
  uart = "qdf2400_e44";
  }
 
- if (xgene_8250_erratum_present(table))
+ if (xgene_8250_erratum_present(table)) {
  iotype = "mmio32";
 
  /* for xgene v1 and v2 we don't know the clock rate of the
Signature · 12 lines
2.7.4

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
#4 lore raw
Quoted 16 lines · Geert Uytterhoeven

Hi Rafael,

Quoted 13 lines · Rafael J. Wysocki
Quoted 12 lines · CEST Mark Brown

--xqegarazqzvkdxmo
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Tue, Aug 15, 2017 at 11:49:36AM +0100, Build bot for Mark Brown wrote:

Today's -next fails to build on arm64 due to:

Quoted 4 lines

arm64-allmodconfig
arm64-defconfig
../drivers/acpi/spcr.c:168:1: error: expected expression before '<<' token ../drivers/acpi/spcr.c:198:1: error: expected expression before '>>' token

Quoted 7 lines
Quoted 5 lines
Quoted 2 lines

caused by f69ba1326ac33b (Merge branch 'acpi-spcr' into linux-next) which has an unresolved conflict in it.

Yes, I broke this, sorry.

Will fix it shortly.

The rebased version (fix?) lacks a curly opening brace. Gmail-whitespace-damaged patch to fold into the bad version below.

OK, should be fixed now.

Sorry for breaking it again.

Thanks,
Rafael