linaro-kernel

linaro-kernel@lists.linaro.org

10095 discussions

master build: 0 failures 3 warnings (v4.7-rc3-70-g41ef721)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.7-rc3-70-g41ef721 Commit: 41ef72181a Merge tag 'nfsd-4.7-1' of git://linux-nfs.org/~bfields/linux Build Time: 154 min 41 sec Passed: 9 / 9 (100.00 %) Failed: 0 / 9 ( 0.00 %) Errors: 0 Warnings: 3 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 3 warnings 0 mismatches : arm64-allmodconfig 1 warnings 0 mismatches : arm64-defconfig ------------------------------------------------------------------------------- Warnings Summary: 3 2 ../drivers/xen/balloon.c:154:13: warning: 'release_memory_resource' declared 'static' but never defined [-Wunused-function] 1 ../fs/reiserfs/ibalance.c:1156:2: warning: 'new_insert_key' may be used uninitialized in this function [-Wmaybe-uninitialized] 1 ../drivers/staging/iio/adc/ad7606_spi.c:24:18: warning: 'data' may be used uninitialized in this function [-Wmaybe-uninitialized] =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm64-allmodconfig : PASS, 0 errors, 3 warnings, 0 section mismatches Warnings: ../fs/reiserfs/ibalance.c:1156:2: warning: 'new_insert_key' may be used uninitialized in this function [-Wmaybe-uninitialized] ../drivers/staging/iio/adc/ad7606_spi.c:24:18: warning: 'data' may be used uninitialized in this function [-Wmaybe-uninitialized] ../drivers/xen/balloon.c:154:13: warning: 'release_memory_resource' declared 'static' but never defined [-Wunused-function] ------------------------------------------------------------------------------- arm64-defconfig : PASS, 0 errors, 1 warnings, 0 section mismatches Warnings: ../drivers/xen/balloon.c:154:13: warning: 'release_memory_resource' declared 'static' but never defined [-Wunused-function] ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allmodconfig arm-allnoconfig x86_64-allnoconfig

9 years, 3 months

[PATCH] arm64: kgdb: Match pstate size with gdbserver protocol

by Daniel Thompson

Current versions of gdb do not interoperate cleanly with kgdb on arm64 systems because gdb and kgdb do not use the same register description. This patch modifies kgdb to work with recent releases of gdb (>= 7.8.1). Compatibility with gdb (after the patch is applied) is as follows: gdb-7.6 and earlier Ok gdb-7.7 series Works if user provides custom target description gdb-7.8(.0) Works if user provides custom target description gdb-7.8.1 and later Ok When commit 44679a4f142b ("arm64: KGDB: Add step debugging support") was introduced it was paired with a gdb patch that made an incompatible change to the gdbserver protocol. This patch was eventually merged into the gdb sources: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=a4d9ba8… The change to the protocol was mostly made to simplify big-endian support inside the kernel gdb stub. Unfortunately the gdb project released gdb-7.7.x and gdb-7.8.0 before the protocol incompatibility was identified and reversed: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=bdc1441… This leaves us in a position where kgdb still uses the no-longer-used protocol; gdb-7.8.1, which restored the original behaviour,If was released on 2014-10-29. I don't believe it is possible to detect/correct the protocol incompatiblity which means the kernel must take a view about which version of the gdb remote protocol is "correct". This patch takes the view that the original/current version of the protocol is correct and that version found in gdb-7.7.x and gdb-7.8.0 is anomalous. Signed-off-by: Daniel Thompson <daniel.thompson(a)linaro.org> --- Notes: Vijaya: I really hope I have the history lesson in the commit message correct! I've done a fair bit of archeology to unpick things. arch/arm64/include/asm/kgdb.h | 13 +++++-------- arch/arm64/kernel/kgdb.c | 7 ++++++- 2 files changed, 11 insertions(+), 9 deletions(-) diff --git a/arch/arm64/include/asm/kgdb.h b/arch/arm64/include/asm/kgdb.h index f69f69c8120c..326fa8f44da5 100644 --- a/arch/arm64/include/asm/kgdb.h +++ b/arch/arm64/include/asm/kgdb.h @@ -43,20 +43,17 @@ extern int kgdb_fault_expected; * General purpose regs: * r0-r30: 64 bit * sp,pc : 64 bit - * pstate : 64 bit - * Total: 34 + * pstate : 32 bit + * Total: 33 + 1 * FPU regs: * f0-f31: 128 bit - * Total: 32 - * Extra regs * fpsr & fpcr: 32 bit - * Total: 2 - * + * Total: 32 + 2 */ -#define _GP_REGS 34 +#define _GP_REGS 33 #define _FP_REGS 32 -#define _EXTRA_REGS 2 +#define _EXTRA_REGS 3 /* * general purpose registers size in bytes. * pstate is only 4 bytes. subtract 4 bytes diff --git a/arch/arm64/kernel/kgdb.c b/arch/arm64/kernel/kgdb.c index b67531a13136..ec62a4e3c190 100644 --- a/arch/arm64/kernel/kgdb.c +++ b/arch/arm64/kernel/kgdb.c @@ -58,7 +58,11 @@ struct dbg_reg_def_t dbg_reg_def[DBG_MAX_REG_NUM] = { { "x30", 8, offsetof(struct pt_regs, regs[30])}, { "sp", 8, offsetof(struct pt_regs, sp)}, { "pc", 8, offsetof(struct pt_regs, pc)}, - { "pstate", 8, offsetof(struct pt_regs, pstate)}, + { "pstate", 4, offsetof(struct pt_regs, pstate) +#ifdef CONFIG_CPU_BIG_ENDIAN + + 4 +#endif + }, { "v0", 16, -1 }, { "v1", 16, -1 }, { "v2", 16, -1 }, @@ -128,6 +132,7 @@ sleeping_thread_to_gdb_regs(unsigned long *gdb_regs, struct task_struct *task) memset((char *)gdb_regs, 0, NUMREGBYTES); thread_regs = task_pt_regs(task); memcpy((void *)gdb_regs, (void *)thread_regs->regs, GP_REG_BYTES); + dbg_get_reg(33, gdb_regs + GP_REG_BYTES, thread_regs); } void kgdb_arch_set_pc(struct pt_regs *regs, unsigned long pc) -- 2.5.5

9 years, 3 months

[PATCH V2] PM / OPP: 'UNKNOWN' status of opp-table->shared

by Viresh Kumar

dev_pm_opp_get_sharing_cpus() returns 0 even in the case where the OPP core doesn't know if the table is shared or not. It is working for most of the platforms, as the OPP table was never created and we returned -ENODEV then. But in case of one of the platforms (Jetson TK1) at least, the situation is a bit different. The OPP table is created (somehow) before dev_pm_opp_get_sharing_cpus() is called and so we returned 0. The caller of this routine treated that as 'CPUs don't share OPPs' and that had bad consequences on performance. Fix this by creating a converting 'shared_opp' to an enum. dev_pm_opp_get_sharing_cpus() returns -EINVAL now in case the status in access-unknown, so that the caller can handle it accordingly (cpufreq-dt considers that as 'all CPUs share the table'). Fixes: 6f707daa3833 ("PM / OPP: Add dev_pm_opp_get_sharing_cpus()") Reported-and-tested-by: Alexandre Courbot <acourbot(a)nvidia.com> Signed-off-by: Viresh Kumar <viresh.kumar(a)linaro.org> --- V2: - Use enum instead of macros. - 0 is used for unknown now, and so no need to initialize it. drivers/base/power/opp/cpu.c | 12 +++++++++--- drivers/base/power/opp/of.c | 10 ++++++++-- drivers/base/power/opp/opp.h | 8 +++++++- 3 files changed, 24 insertions(+), 6 deletions(-) diff --git a/drivers/base/power/opp/cpu.c b/drivers/base/power/opp/cpu.c index 83d6e7ba1a34..8c3434bdb26d 100644 --- a/drivers/base/power/opp/cpu.c +++ b/drivers/base/power/opp/cpu.c @@ -211,7 +211,7 @@ int dev_pm_opp_set_sharing_cpus(struct device *cpu_dev, } /* Mark opp-table as multiple CPUs are sharing it now */ - opp_table->shared_opp = true; + opp_table->shared_opp = OPP_TABLE_ACCESS_SHARED; } unlock: mutex_unlock(&opp_table_lock); @@ -227,7 +227,8 @@ EXPORT_SYMBOL_GPL(dev_pm_opp_set_sharing_cpus); * * This updates the @cpumask with CPUs that are sharing OPPs with @cpu_dev. * - * Returns -ENODEV if OPP table isn't already present. + * Returns -ENODEV if OPP table isn't already present and -EINVAL if the OPP + * table's status is access-unknown. * * Locking: The internal opp_table and opp structures are RCU protected. * Hence this function internally uses RCU updater strategy with mutex locks @@ -249,9 +250,14 @@ int dev_pm_opp_get_sharing_cpus(struct device *cpu_dev, struct cpumask *cpumask) goto unlock; } + if (opp_table->shared_opp == OPP_TABLE_ACCESS_UNKNOWN) { + ret = -EINVAL; + goto unlock; + } + cpumask_clear(cpumask); - if (opp_table->shared_opp) { + if (opp_table->shared_opp == OPP_TABLE_ACCESS_SHARED) { list_for_each_entry(opp_dev, &opp_table->dev_list, node) cpumask_set_cpu(opp_dev->dev->id, cpumask); } else { diff --git a/drivers/base/power/opp/of.c b/drivers/base/power/opp/of.c index 94d2010558e3..1dfd3dd92624 100644 --- a/drivers/base/power/opp/of.c +++ b/drivers/base/power/opp/of.c @@ -34,7 +34,10 @@ static struct opp_table *_managed_opp(const struct device_node *np) * But the OPPs will be considered as shared only if the * OPP table contains a "opp-shared" property. */ - return opp_table->shared_opp ? opp_table : NULL; + if (opp_table->shared_opp == OPP_TABLE_ACCESS_SHARED) + return opp_table; + + return NULL; } } @@ -353,7 +356,10 @@ static int _of_add_opp_table_v2(struct device *dev, struct device_node *opp_np) } opp_table->np = opp_np; - opp_table->shared_opp = of_property_read_bool(opp_np, "opp-shared"); + if (of_property_read_bool(opp_np, "opp-shared")) + opp_table->shared_opp = OPP_TABLE_ACCESS_SHARED; + else + opp_table->shared_opp = OPP_TABLE_ACCESS_EXCLUSIVE; mutex_unlock(&opp_table_lock); diff --git a/drivers/base/power/opp/opp.h b/drivers/base/power/opp/opp.h index 20f3be22e060..fabd5ca1a083 100644 --- a/drivers/base/power/opp/opp.h +++ b/drivers/base/power/opp/opp.h @@ -119,6 +119,12 @@ struct opp_device { #endif }; +enum opp_table_access { + OPP_TABLE_ACCESS_UNKNOWN = 0, + OPP_TABLE_ACCESS_EXCLUSIVE = 1, + OPP_TABLE_ACCESS_SHARED = 2, +}; + /** * struct opp_table - Device opp structure * @node: table node - contains the devices with OPPs that @@ -166,7 +172,7 @@ struct opp_table { /* For backward compatibility with v1 bindings */ unsigned int voltage_tolerance_v1; - bool shared_opp; + enum opp_table_access shared_opp; struct dev_pm_opp *suspend_opp; unsigned int *supported_hw; -- 2.7.1.410.g6faf27b

9 years, 3 months

[PATCH] PM / OPP: 'UNKNOWN' status of opp-table->shared

by Viresh Kumar

dev_pm_opp_get_sharing_cpus() returns 0 even in the case where the OPP core doesn't know if the table is shared or not. It is working for most of the platforms, as the OPP table was never created and we returned -ENODEV then. But in case of one of the platforms (Jetson TK1) at least, the situation is a bit different. The OPP table is created (somehow) before dev_pm_opp_get_sharing_cpus() is called and so we returned 0. The caller of this routine treated that as 'CPUs don't share OPPs' and that had bad consequences on performance. Fix this by converting 'shared_opp' to an integer and have an extra value when its state in undefined. dev_pm_opp_get_sharing_cpus() returns -EINVAL now in that case, so that the caller can handle it accordingly (cpufreq-dt considers that as 'all CPUs share the table'). Fixes: 6f707daa3833 ("PM / OPP: Add dev_pm_opp_get_sharing_cpus()") Reported-by: Alexandre Courbot <acourbot(a)nvidia.com> Signed-off-by: Viresh Kumar <viresh.kumar(a)linaro.org> --- Hi Alexandre, This is untested, can you please confirm if this fixes it for you? drivers/base/power/opp/core.c | 3 +++ drivers/base/power/opp/cpu.c | 12 +++++++++--- drivers/base/power/opp/of.c | 10 ++++++++-- drivers/base/power/opp/opp.h | 5 ++++- 4 files changed, 24 insertions(+), 6 deletions(-) diff --git a/drivers/base/power/opp/core.c b/drivers/base/power/opp/core.c index 7c04c87738a6..14d212885098 100644 --- a/drivers/base/power/opp/core.c +++ b/drivers/base/power/opp/core.c @@ -764,6 +764,9 @@ static struct opp_table *_add_opp_table(struct device *dev) /* Set regulator to a non-NULL error value */ opp_table->regulator = ERR_PTR(-ENXIO); + /* Set sharing information as unknown */ + opp_table->shared_opp = OPP_TABLE_SHARED_UNKNOWN; + /* Find clk for the device */ opp_table->clk = clk_get(dev, NULL); if (IS_ERR(opp_table->clk)) { diff --git a/drivers/base/power/opp/cpu.c b/drivers/base/power/opp/cpu.c index 83d6e7ba1a34..4ca86df8a451 100644 --- a/drivers/base/power/opp/cpu.c +++ b/drivers/base/power/opp/cpu.c @@ -211,7 +211,7 @@ int dev_pm_opp_set_sharing_cpus(struct device *cpu_dev, } /* Mark opp-table as multiple CPUs are sharing it now */ - opp_table->shared_opp = true; + opp_table->shared_opp = OPP_TABLE_IS_SHARED; } unlock: mutex_unlock(&opp_table_lock); @@ -227,7 +227,8 @@ EXPORT_SYMBOL_GPL(dev_pm_opp_set_sharing_cpus); * * This updates the @cpumask with CPUs that are sharing OPPs with @cpu_dev. * - * Returns -ENODEV if OPP table isn't already present. + * Returns -ENODEV if OPP table isn't already present and -EINVAL if the OPP + * table's status is shared-unknown. * * Locking: The internal opp_table and opp structures are RCU protected. * Hence this function internally uses RCU updater strategy with mutex locks @@ -249,9 +250,14 @@ int dev_pm_opp_get_sharing_cpus(struct device *cpu_dev, struct cpumask *cpumask) goto unlock; } + if (opp_table->shared_opp == OPP_TABLE_SHARED_UNKNOWN) { + ret = -EINVAL; + goto unlock; + } + cpumask_clear(cpumask); - if (opp_table->shared_opp) { + if (opp_table->shared_opp == OPP_TABLE_IS_SHARED) { list_for_each_entry(opp_dev, &opp_table->dev_list, node) cpumask_set_cpu(opp_dev->dev->id, cpumask); } else { diff --git a/drivers/base/power/opp/of.c b/drivers/base/power/opp/of.c index 94d2010558e3..83ad3a6a16f1 100644 --- a/drivers/base/power/opp/of.c +++ b/drivers/base/power/opp/of.c @@ -34,7 +34,10 @@ static struct opp_table *_managed_opp(const struct device_node *np) * But the OPPs will be considered as shared only if the * OPP table contains a "opp-shared" property. */ - return opp_table->shared_opp ? opp_table : NULL; + if (opp_table->shared_opp == OPP_TABLE_IS_SHARED) + return opp_table; + + return NULL; } } @@ -353,7 +356,10 @@ static int _of_add_opp_table_v2(struct device *dev, struct device_node *opp_np) } opp_table->np = opp_np; - opp_table->shared_opp = of_property_read_bool(opp_np, "opp-shared"); + if (of_property_read_bool(opp_np, "opp-shared")) + opp_table->shared_opp = OPP_TABLE_IS_SHARED; + else + opp_table->shared_opp = OPP_TABLE_IS_NOT_SHARED; mutex_unlock(&opp_table_lock); diff --git a/drivers/base/power/opp/opp.h b/drivers/base/power/opp/opp.h index 20f3be22e060..ffd0b54e7894 100644 --- a/drivers/base/power/opp/opp.h +++ b/drivers/base/power/opp/opp.h @@ -166,7 +166,10 @@ struct opp_table { /* For backward compatibility with v1 bindings */ unsigned int voltage_tolerance_v1; - bool shared_opp; +#define OPP_TABLE_IS_NOT_SHARED 0 +#define OPP_TABLE_IS_SHARED 1 +#define OPP_TABLE_SHARED_UNKNOWN UINT_MAX + unsigned int shared_opp; struct dev_pm_opp *suspend_opp; unsigned int *supported_hw; -- 2.7.1.410.g6faf27b

9 years, 3 months

master build: 0 failures 3 warnings (v4.7-rc3-55-gd325ea8)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.7-rc3-55-gd325ea8 Commit: d325ea8594 Merge tag 'drm-fixes-for-v4.7-rc4' of git://people.freedesktop.org/~airlied/linux Build Time: 81 min 12 sec Passed: 9 / 9 (100.00 %) Failed: 0 / 9 ( 0.00 %) Errors: 0 Warnings: 3 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 3 warnings 0 mismatches : arm64-allmodconfig 1 warnings 0 mismatches : arm64-defconfig ------------------------------------------------------------------------------- Warnings Summary: 3 2 ../drivers/xen/balloon.c:154:13: warning: 'release_memory_resource' declared 'static' but never defined [-Wunused-function] 1 ../fs/reiserfs/ibalance.c:1156:2: warning: 'new_insert_key' may be used uninitialized in this function [-Wmaybe-uninitialized] 1 ../drivers/staging/iio/adc/ad7606_spi.c:24:18: warning: 'data' may be used uninitialized in this function [-Wmaybe-uninitialized] =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm64-allmodconfig : PASS, 0 errors, 3 warnings, 0 section mismatches Warnings: ../fs/reiserfs/ibalance.c:1156:2: warning: 'new_insert_key' may be used uninitialized in this function [-Wmaybe-uninitialized] ../drivers/staging/iio/adc/ad7606_spi.c:24:18: warning: 'data' may be used uninitialized in this function [-Wmaybe-uninitialized] ../drivers/xen/balloon.c:154:13: warning: 'release_memory_resource' declared 'static' but never defined [-Wunused-function] ------------------------------------------------------------------------------- arm64-defconfig : PASS, 0 errors, 1 warnings, 0 section mismatches Warnings: ../drivers/xen/balloon.c:154:13: warning: 'release_memory_resource' declared 'static' but never defined [-Wunused-function] ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allmodconfig arm-allnoconfig x86_64-allnoconfig

9 years, 3 months

next-20160616 build: 1 failures 9 warnings (next-20160616)

by Build bot for Mark Brown

Tree/Branch: next-20160616 Git describe: next-20160616 Commit: 649a37133c Add linux-next specific files for 20160616 Build Time: 166 min 21 sec Passed: 8 / 9 ( 88.89 %) Failed: 1 / 9 ( 11.11 %) Errors: 1 Warnings: 9 Section Mismatches: 0 Failed defconfigs: arm-allmodconfig Errors: arm-allmodconfig ../include/linux/compiler-gcc.h:243:38: error: impossible constraint in 'asm' ../include/linux/compiler-gcc.h:243:38: error: impossible constraint in 'asm' ../include/linux/compiler-gcc.h:243:38: error: impossible constraint in 'asm' ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 7 warnings 0 mismatches : arm64-allmodconfig 2 warnings 0 mismatches : arm-multi_v7_defconfig 71 warnings 0 mismatches : arm-allmodconfig 2 warnings 0 mismatches : arm64-defconfig ------------------------------------------------------------------------------- Errors summary: 1 3 ../include/linux/compiler-gcc.h:243:38: error: impossible constraint in 'asm' Warnings Summary: 9 66 ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints 4 ../drivers/clk/sunxi/clk-sun4i-tcon-ch1.c:82:6: warning: unused variable 'num_parents' [-Wunused-variable] 3 ../drivers/net/phy/mdio-mux.c:188:3: warning: 'parent_bus_node' may be used uninitialized in this function [-Wmaybe-uninitialized] 2 ../include/linux/kfifo.h:403:39: warning: 'ge.id' may be used uninitialized in this function [-Wmaybe-uninitialized] 2 ../include/linux/dynamic_debug.h:134:3: warning: 'carrier_offset' may be used uninitialized in this function [-Wmaybe-uninitialized] 2 ../drivers/staging/ks7010/ks7010_config.c:263:8: warning: assignment discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] 1 ../include/linux/of.h:1002:20: warning: comparison of distinct pointer types lacks a cast 1 ../include/linux/kernel.h:743:17: warning: comparison of distinct pointer types lacks a cast 1 ../drivers/staging/iio/adc/ad7606_spi.c:24:18: warning: 'data' may be used uninitialized in this function [-Wmaybe-uninitialized] =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm64-allmodconfig : PASS, 0 errors, 7 warnings, 0 section mismatches Warnings: ../drivers/clk/sunxi/clk-sun4i-tcon-ch1.c:82:6: warning: unused variable 'num_parents' [-Wunused-variable] ../include/linux/kernel.h:743:17: warning: comparison of distinct pointer types lacks a cast ../include/linux/kfifo.h:403:39: warning: 'ge.id' may be used uninitialized in this function [-Wmaybe-uninitialized] ../include/linux/dynamic_debug.h:134:3: warning: 'carrier_offset' may be used uninitialized in this function [-Wmaybe-uninitialized] ../drivers/staging/iio/adc/ad7606_spi.c:24:18: warning: 'data' may be used uninitialized in this function [-Wmaybe-uninitialized] ../drivers/staging/ks7010/ks7010_config.c:263:8: warning: assignment discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] ../drivers/net/phy/mdio-mux.c:188:3: warning: 'parent_bus_node' may be used uninitialized in this function [-Wmaybe-uninitialized] ------------------------------------------------------------------------------- arm-multi_v7_defconfig : PASS, 0 errors, 2 warnings, 0 section mismatches Warnings: ../drivers/clk/sunxi/clk-sun4i-tcon-ch1.c:82:6: warning: unused variable 'num_parents' [-Wunused-variable] ../drivers/net/phy/mdio-mux.c:188:3: warning: 'parent_bus_node' may be used uninitialized in this function [-Wmaybe-uninitialized] ------------------------------------------------------------------------------- arm-allmodconfig : FAIL, 3 errors, 71 warnings, 0 section mismatches Errors: ../include/linux/compiler-gcc.h:243:38: error: impossible constraint in 'asm' ../include/linux/compiler-gcc.h:243:38: error: impossible constraint in 'asm' ../include/linux/compiler-gcc.h:243:38: error: impossible constraint in 'asm' Warnings: ../include/linux/of.h:1002:20: warning: comparison of distinct pointer types lacks a cast ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../include/linux/compiler-gcc.h:243:38: warning: asm operand 0 probably doesn't match constraints ../drivers/clk/sunxi/clk-sun4i-tcon-ch1.c:82:6: warning: unused variable 'num_parents' [-Wunused-variable] ../include/linux/dynamic_debug.h:134:3: warning: 'carrier_offset' may be used uninitialized in this function [-Wmaybe-uninitialized] ../drivers/staging/ks7010/ks7010_config.c:263:8: warning: assignment discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] ../drivers/net/phy/mdio-mux.c:188:3: warning: 'parent_bus_node' may be used uninitialized in this function [-Wmaybe-uninitialized] ------------------------------------------------------------------------------- arm64-defconfig : PASS, 0 errors, 2 warnings, 0 section mismatches Warnings: ../drivers/clk/sunxi/clk-sun4i-tcon-ch1.c:82:6: warning: unused variable 'num_parents' [-Wunused-variable] ../include/linux/kfifo.h:403:39: warning: 'ge.id' may be used uninitialized in this function [-Wmaybe-uninitialized] ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: x86_64-allnoconfig arm64-allnoconfig arm-allnoconfig arm-multi_v5_defconfig x86_64-defconfig close failed in file object destructor: sys.excepthook is missing lost sys.stderr

9 years, 3 months

[GIT PULL] [lsk-v3.18-android] linaro-android v3.18 topic branch updates

by Amit Pundir

Hi Alex, Mark, Please consider following linaro-android pull request for "linux-linaro-lsk-v3.18-android" LSK branch. Regards, Amit Pundir The following changes since commit a4b4755eb2cf335c47738ad98968eba6d5117381: UPSTREAM: android: binder: fix binder mmap failures (2016-05-26 14:04:58 +0530) are available in the git repository at: git://android.git.linaro.org/kernel/linaro-android.git lsk-v3.18-android for you to fetch changes up to ba0f321f1537d64f8dfaabd8a562fdc825f13436: ANDROID: dm verity fec: add missing release from fec_ktype (2016-06-16 15:11:57 +0530) ---------------------------------------------------------------- Badhri Jagan Sridharan (1): ANDROID: dm: use default verity public key Ben Hutchings (1): BACKPORT: perf tools: Document the perf sysctls Jeff Vander Stoep (2): FROMLIST: security,perf: Allow further restriction of perf_event_open ANDROID: restrict access to perf events Sami Tolvanen (2): ANDROID: dm verity fec: limit error correction recursion ANDROID: dm verity fec: add missing release from fec_ktype Documentation/sysctl/kernel.txt | 43 +++++++++++++++++++++++++++++-------------- android/configs/android-base.cfg | 1 + drivers/md/dm-android-verity.c | 67 +++++++++++++++++++++++++++++++++++++++++++++++-------------------- drivers/md/dm-android-verity.h | 16 ++++++++++++++++ drivers/md/dm-verity-fec.c | 14 ++++++++++++-- drivers/md/dm-verity-fec.h | 4 ++++ include/linux/perf_event.h | 5 +++++ kernel/events/core.c | 8 ++++++++ security/Kconfig | 9 +++++++++ tools/perf/util/evsel.c | 15 +++++++++------ 10 files changed, 140 insertions(+), 42 deletions(-)

9 years, 3 months

[GIT PULL] [lsk-v4.4-android] linaro-android v4.4 topic branch updates

by Amit Pundir

Hi Alex, Mark, Please consider following linaro-android pull request for "linux-linaro-lsk-v4.4-android" LSK branch. Regards, Amit Pundir The following changes since commit 9ad8208bd7d0a5d9e232142d95f94bddc35ffff7: Merge branch 'linux-linaro-lsk-v4.4' into linux-linaro-lsk-v4.4-android (2016-06-14 17:08:03 +0800) are available in the git repository at: git://android.git.linaro.org/kernel/linaro-android.git lsk-v4.4-android for you to fetch changes up to 5db5b648730e1d70d07bfa21c28854c05d8d0329: ANDROID: dm verity fec: add missing release from fec_ktype (2016-06-16 13:45:07 +0530) ---------------------------------------------------------------- Amit Pundir (2): Revert "arm: dcc_tty: fix armv6 dcc tty build failure" Revert "armv6 dcc tty driver" Ben Hutchings (1): BACKPORT: perf tools: Document the perf sysctls Dmitry Shmidt (1): ARM64: Ignore Image-dtb from git point of view Haojian Zhuang (1): arm64: add option to build Image-dtb Jeff Vander Stoep (2): FROMLIST: security,perf: Allow further restriction of perf_event_open ANDROID: restrict access to perf events Sami Tolvanen (2): ANDROID: dm verity fec: limit error correction recursion ANDROID: dm verity fec: add missing release from fec_ktype Winter Wang (1): ANDROID: usb: gadget: f_midi: set fi->f to NULL when free f_midi function Documentation/sysctl/kernel.txt | 15 ++++++ android/configs/android-base.cfg | 1 + arch/arm64/Makefile | 2 +- arch/arm64/boot/.gitignore | 1 + arch/arm64/boot/Makefile | 3 ++ drivers/char/Kconfig | 4 -- drivers/char/Makefile | 1 - drivers/char/dcc_tty.c | 326 --------------------------------------------------------------------------------------------------------------------------- drivers/md/dm-verity-fec.c | 14 +++++- drivers/md/dm-verity-fec.h | 4 ++ drivers/usb/gadget/function/f_midi.c | 1 + include/linux/perf_event.h | 5 ++ kernel/events/core.c | 8 +++ security/Kconfig | 9 ++++ tools/perf/util/evsel.c | 15 +++--- 15 files changed, 69 insertions(+), 340 deletions(-) delete mode 100644 drivers/char/dcc_tty.c

9 years, 3 months

master build: 0 failures 3 warnings (v4.7-rc3-22-gabd3830)

by Build bot for Mark Brown

Tree/Branch: master Git describe: v4.7-rc3-22-gabd3830 Commit: abd3830163 Merge tag 'upstream-4.7-rc4' of git://git.infradead.org/linux-ubifs Build Time: 131 min 37 sec Passed: 9 / 9 (100.00 %) Failed: 0 / 9 ( 0.00 %) Errors: 0 Warnings: 3 Section Mismatches: 0 ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 3 warnings 0 mismatches : arm64-allmodconfig 1 warnings 0 mismatches : arm64-defconfig ------------------------------------------------------------------------------- Warnings Summary: 3 2 ../drivers/xen/balloon.c:154:13: warning: 'release_memory_resource' declared 'static' but never defined [-Wunused-function] 1 ../fs/reiserfs/ibalance.c:1156:2: warning: 'new_insert_key' may be used uninitialized in this function [-Wmaybe-uninitialized] 1 ../drivers/staging/iio/adc/ad7606_spi.c:24:18: warning: 'data' may be used uninitialized in this function [-Wmaybe-uninitialized] =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- arm64-allmodconfig : PASS, 0 errors, 3 warnings, 0 section mismatches Warnings: ../fs/reiserfs/ibalance.c:1156:2: warning: 'new_insert_key' may be used uninitialized in this function [-Wmaybe-uninitialized] ../drivers/staging/iio/adc/ad7606_spi.c:24:18: warning: 'data' may be used uninitialized in this function [-Wmaybe-uninitialized] ../drivers/xen/balloon.c:154:13: warning: 'release_memory_resource' declared 'static' but never defined [-Wunused-function] ------------------------------------------------------------------------------- arm64-defconfig : PASS, 0 errors, 1 warnings, 0 section mismatches Warnings: ../drivers/xen/balloon.c:154:13: warning: 'release_memory_resource' declared 'static' but never defined [-Wunused-function] ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches: arm64-allnoconfig arm-multi_v5_defconfig arm-multi_v7_defconfig x86_64-defconfig arm-allmodconfig arm-allnoconfig x86_64-allnoconfig close failed in file object destructor: sys.excepthook is missing lost sys.stderr

9 years, 3 months

v3.2.81 build: 2 failures 32 warnings (v3.2.81)

by Build bot for Mark Brown

Tree/Branch: v3.2.81 Git describe: v3.2.81 Commit: c5d5c18b21 Linux 3.2.81 Build Time: 0 min 15 sec Passed: 2 / 4 ( 50.00 %) Failed: 2 / 4 ( 50.00 %) Errors: 4 Warnings: 32 Section Mismatches: 0 Failed defconfigs: arm-allmodconfig arm-allnoconfig Errors: arm-allnoconfig /home/broonie/build/linux-stable/arch/arm/include/asm/div64.h:77:7: error: '__LINUX_ARM_ARCH__' undeclared (first use in this function) /home/broonie/build/linux-stable/arch/arm/include/asm/glue-cache.h:129:2: error: #error Unknown cache maintenance model /home/broonie/build/linux-stable/arch/arm/include/asm/glue-df.h:107:2: error: #error Unknown data abort handler type /home/broonie/build/linux-stable/arch/arm/include/asm/glue-pf.h:54:2: error: #error Unknown prefetch abort handler type ------------------------------------------------------------------------------- defconfigs with issues (other than build errors): 7 warnings 0 mismatches : x86_64-allnoconfig 2 warnings 0 mismatches : arm-allmodconfig 19 warnings 0 mismatches : arm-allnoconfig 9 warnings 0 mismatches : x86_64-defconfig ------------------------------------------------------------------------------- Errors summary: 4 1 /home/broonie/build/linux-stable/arch/arm/include/asm/glue-pf.h:54:2: error: #error Unknown prefetch abort handler type 1 /home/broonie/build/linux-stable/arch/arm/include/asm/glue-df.h:107:2: error: #error Unknown data abort handler type 1 /home/broonie/build/linux-stable/arch/arm/include/asm/glue-cache.h:129:2: error: #error Unknown cache maintenance model 1 /home/broonie/build/linux-stable/arch/arm/include/asm/div64.h:77:7: error: '__LINUX_ARM_ARCH__' undeclared (first use in this function) Warnings Summary: 32 2 /home/broonie/build/linux-stable/mm/slub.c:4476:11: warning: 'x' may be used uninitialized in this function [-Wmaybe-uninitialized] 2 /home/broonie/build/linux-stable/fs/namespace.c:2556:8: warning: 'kernel_type' may be used uninitialized in this function [-Wmaybe-uninitialized] 2 /home/broonie/build/linux-stable/fs/namespace.c:2556:8: warning: 'kernel_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] 2 /home/broonie/build/linux-stable/drivers/usb/host/ohci-dbg.c:77:11: warning: the comparison will always evaluate as 'true' for the address of 'next' will never be NULL [-Waddress] 2 .config:27:warning: symbol value '' invalid for PHYS_OFFSET 1 /home/broonie/build/linux-stable/kernel/sched.c:1889:13: warning: 'update_idle_cpu_load' declared 'static' but never defined [-Wunused-function] 1 /home/broonie/build/linux-stable/include/linux/blkdev.h:1291:39: warning: statement with no effect [-Wunused-value] 1 /home/broonie/build/linux-stable/fs/compat_ioctl.c:611:38: warning: typedef 'SS' locally defined but not used [-Wunused-local-typedefs] 1 /home/broonie/build/linux-stable/drivers/gpu/drm/i915/i915_drv.c:975:0: warning: "NEEDS_FORCE_WAKE" redefined 1 /home/broonie/build/linux-stable/drivers/acpi/acpica/nsrepair.c:199:21: warning: 'new_object' may be used uninitialized in this function [-Wmaybe-uninitialized] 1 /home/broonie/build/linux-stable/arch/x86/kernel/quirks.c:407:21: warning: 'val' may be used uninitialized in this function [-Wmaybe-uninitialized] 1 /home/broonie/build/linux-stable/arch/x86/kernel/quirks.c:367:4: warning: 'd' may be used uninitialized in this function [-Wmaybe-uninitialized] 1 /home/broonie/build/linux-stable/arch/x86/kernel/quirks.c:361:4: warning: 'b' is used uninitialized in this function [-Wuninitialized] 1 /home/broonie/build/linux-stable/arch/arm/include/asm/system.h:342:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] 1 /home/broonie/build/linux-stable/arch/arm/include/asm/system.h:272:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] 1 /home/broonie/build/linux-stable/arch/arm/include/asm/system.h:265:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] 1 /home/broonie/build/linux-stable/arch/arm/include/asm/system.h:131:35: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] 1 /home/broonie/build/linux-stable/arch/arm/include/asm/system.h:127:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] 1 /home/broonie/build/linux-stable/arch/arm/include/asm/system.h:121:3: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] 1 /home/broonie/build/linux-stable/arch/arm/include/asm/system.h:120:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] 1 /home/broonie/build/linux-stable/arch/arm/include/asm/system.h:114:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] 1 /home/broonie/build/linux-stable/arch/arm/include/asm/swab.h:25:28: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] 1 /home/broonie/build/linux-stable/arch/arm/include/asm/processor.h:82:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] 1 /home/broonie/build/linux-stable/arch/arm/include/asm/processor.h:102:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] 1 /home/broonie/build/linux-stable/arch/arm/include/asm/irqflags.h:11:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] 1 /home/broonie/build/linux-stable/arch/arm/include/asm/fpstate.h:32:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] 1 /home/broonie/build/linux-stable/arch/arm/include/asm/cachetype.h:33:7: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] 1 /home/broonie/build/linux-stable/arch/arm/include/asm/cachetype.h:28:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] 1 /home/broonie/build/linux-stable/arch/arm/include/asm/cacheflush.h:196:7: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] 1 /home/broonie/build/linux-stable/arch/arm/include/asm/cacheflush.h:194:7: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] 1 /home/broonie/build/linux-stable/arch/arm/include/asm/bitops.h:217:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] 1 /home/broonie/build/linux-stable/arch/arm/include/asm/atomic.h:30:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] =============================================================================== Detailed per-defconfig build reports below: ------------------------------------------------------------------------------- x86_64-allnoconfig : PASS, 0 errors, 7 warnings, 0 section mismatches Warnings: /home/broonie/build/linux-stable/kernel/sched.c:1889:13: warning: 'update_idle_cpu_load' declared 'static' but never defined [-Wunused-function] /home/broonie/build/linux-stable/arch/x86/kernel/quirks.c:361:4: warning: 'b' is used uninitialized in this function [-Wuninitialized] /home/broonie/build/linux-stable/arch/x86/kernel/quirks.c:367:4: warning: 'd' may be used uninitialized in this function [-Wmaybe-uninitialized] /home/broonie/build/linux-stable/arch/x86/kernel/quirks.c:407:21: warning: 'val' may be used uninitialized in this function [-Wmaybe-uninitialized] /home/broonie/build/linux-stable/fs/namespace.c:2556:8: warning: 'kernel_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] /home/broonie/build/linux-stable/fs/namespace.c:2556:8: warning: 'kernel_type' may be used uninitialized in this function [-Wmaybe-uninitialized] /home/broonie/build/linux-stable/mm/slub.c:4476:11: warning: 'x' may be used uninitialized in this function [-Wmaybe-uninitialized] ------------------------------------------------------------------------------- arm-allmodconfig : FAIL, 0 errors, 2 warnings, 0 section mismatches Warnings: .config:27:warning: symbol value '' invalid for PHYS_OFFSET .config:27:warning: symbol value '' invalid for PHYS_OFFSET ------------------------------------------------------------------------------- arm-allnoconfig : FAIL, 4 errors, 19 warnings, 0 section mismatches Errors: /home/broonie/build/linux-stable/arch/arm/include/asm/div64.h:77:7: error: '__LINUX_ARM_ARCH__' undeclared (first use in this function) /home/broonie/build/linux-stable/arch/arm/include/asm/glue-cache.h:129:2: error: #error Unknown cache maintenance model /home/broonie/build/linux-stable/arch/arm/include/asm/glue-df.h:107:2: error: #error Unknown data abort handler type /home/broonie/build/linux-stable/arch/arm/include/asm/glue-pf.h:54:2: error: #error Unknown prefetch abort handler type Warnings: /home/broonie/build/linux-stable/arch/arm/include/asm/irqflags.h:11:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] /home/broonie/build/linux-stable/arch/arm/include/asm/system.h:114:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] /home/broonie/build/linux-stable/arch/arm/include/asm/system.h:120:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] /home/broonie/build/linux-stable/arch/arm/include/asm/system.h:121:3: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] /home/broonie/build/linux-stable/arch/arm/include/asm/system.h:127:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] /home/broonie/build/linux-stable/arch/arm/include/asm/system.h:131:35: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] /home/broonie/build/linux-stable/arch/arm/include/asm/system.h:265:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] /home/broonie/build/linux-stable/arch/arm/include/asm/system.h:272:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] /home/broonie/build/linux-stable/arch/arm/include/asm/system.h:342:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] /home/broonie/build/linux-stable/arch/arm/include/asm/bitops.h:217:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] /home/broonie/build/linux-stable/arch/arm/include/asm/swab.h:25:28: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] /home/broonie/build/linux-stable/arch/arm/include/asm/fpstate.h:32:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] /home/broonie/build/linux-stable/arch/arm/include/asm/processor.h:82:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] /home/broonie/build/linux-stable/arch/arm/include/asm/processor.h:102:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] /home/broonie/build/linux-stable/arch/arm/include/asm/atomic.h:30:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] /home/broonie/build/linux-stable/arch/arm/include/asm/cachetype.h:28:5: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] /home/broonie/build/linux-stable/arch/arm/include/asm/cachetype.h:33:7: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] /home/broonie/build/linux-stable/arch/arm/include/asm/cacheflush.h:194:7: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] /home/broonie/build/linux-stable/arch/arm/include/asm/cacheflush.h:196:7: warning: "__LINUX_ARM_ARCH__" is not defined [-Wundef] ------------------------------------------------------------------------------- x86_64-defconfig : PASS, 0 errors, 9 warnings, 0 section mismatches Warnings: /home/broonie/build/linux-stable/fs/namespace.c:2556:8: warning: 'kernel_dev' may be used uninitialized in this function [-Wmaybe-uninitialized] /home/broonie/build/linux-stable/fs/namespace.c:2556:8: warning: 'kernel_type' may be used uninitialized in this function [-Wmaybe-uninitialized] /home/broonie/build/linux-stable/mm/slub.c:4476:11: warning: 'x' may be used uninitialized in this function [-Wmaybe-uninitialized] /home/broonie/build/linux-stable/drivers/acpi/acpica/nsrepair.c:199:21: warning: 'new_object' may be used uninitialized in this function [-Wmaybe-uninitialized] /home/broonie/build/linux-stable/fs/compat_ioctl.c:611:38: warning: typedef 'SS' locally defined but not used [-Wunused-local-typedefs] /home/broonie/build/linux-stable/drivers/gpu/drm/i915/i915_drv.c:975:0: warning: "NEEDS_FORCE_WAKE" redefined /home/broonie/build/linux-stable/include/linux/blkdev.h:1291:39: warning: statement with no effect [-Wunused-value] /home/broonie/build/linux-stable/drivers/usb/host/ohci-dbg.c:77:11: warning: the comparison will always evaluate as 'true' for the address of 'next' will never be NULL [-Waddress] /home/broonie/build/linux-stable/drivers/usb/host/ohci-dbg.c:77:11: warning: the comparison will always evaluate as 'true' for the address of 'next' will never be NULL [-Waddress] ------------------------------------------------------------------------------- Passed with no errors, warnings or mismatches:

9 years, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

linaro-kernel