linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* linux-next: build failure after merge of the char-misc tree
@ 2020-07-27  8:08 Stephen Rothwell
  2020-07-27  9:24 ` Greg KH
  0 siblings, 1 reply; 51+ messages in thread
From: Stephen Rothwell @ 2020-07-27  8:08 UTC (permalink / raw)
  To: Greg KH, Arnd Bergmann
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Oded Gabbay,
	Omer Shpigelman

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

Hi all,

After merging the char-misc tree, today's linux-next build (x86_64
allmodconfig) failed like this:

In file included from drivers/misc/habanalabs/goya/goya.c:8:
drivers/misc/habanalabs/goya/goyaP.h:12:10: fatal error: habanalabs.h: No such file or directory
   12 | #include "habanalabs.h"
      |          ^~~~~~~~~~~~~~
In file included from drivers/misc/habanalabs/goya/goya_security.c:8:
drivers/misc/habanalabs/goya/goyaP.h:12:10: fatal error: habanalabs.h: No such file or directory
   12 | #include "habanalabs.h"
      |          ^~~~~~~~~~~~~~

Presumably caused by commit

  70b2f993ea4a ("habanalabs: create common folder")

I have used the char-misc tree from next-20200724 for today.
-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 51+ messages in thread
* linux-next: build failure after merge of the char-misc tree
@ 2023-06-26  4:25 Stephen Rothwell
  2023-06-26  9:06 ` Greg KH
  0 siblings, 1 reply; 51+ messages in thread
From: Stephen Rothwell @ 2023-06-26  4:25 UTC (permalink / raw)
  To: Greg KH, Arnd Bergmann
  Cc: Greg Kroah-Hartman, Ivan Orlov, Linux Kernel Mailing List,
	Linux Next Mailing List

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

Hi all,

After merging the char-misc tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:

drivers/char/bsr.c: In function 'bsr_init':
drivers/char/bsr.c:301:13: error: 'err' undeclared (first use in this function)
  301 |         if (err)
      |             ^~~
drivers/char/bsr.c:301:13: note: each undeclared identifier is reported only once for each function it appears in

Caused by commit

  e55ce9fd3d8f ("bsr: make bsr_class a static const structure")

I have reverted that commit for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 51+ messages in thread
* linux-next: build failure after merge of the char-misc tree
@ 2022-05-20  9:46 Stephen Rothwell
  2022-05-20 19:08 ` Greg KH
  0 siblings, 1 reply; 51+ messages in thread
From: Stephen Rothwell @ 2022-05-20  9:46 UTC (permalink / raw)
  To: Greg KH, Arnd Bergmann
  Cc: Samuel Thibault, Linux Kernel Mailing List, Linux Next Mailing List

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

Hi all,

After merging the soundwire tree, today's linux-next build (x86_64
allmodconfig) failed like this:

make[4]: *** Deleting file 'drivers/accessibility/speakup/mapdata.h'
can't open ./include/linux/input.h
make[4]: *** [/home/sfr/next/next/drivers/accessibility/speakup/Makefile:46: drivers/accessibility/speakup/mapdata.h] Error 1
make[3]: *** [/home/sfr/next/next/scripts/Makefile.build:542: drivers/accessibility/speakup] Error 2

Caused by commit

  6646b95aab5f ("speakup: Generate speakupmap.h automatically")

I have used the char-misc tree from next-20220519 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 51+ messages in thread
* linux-next: build failure after merge of the char-misc tree
@ 2022-02-25 20:40 broonie
  2022-02-26 15:08 ` Greg KH
  0 siblings, 1 reply; 51+ messages in thread
From: broonie @ 2022-02-25 20:40 UTC (permalink / raw)
  To: Greg KH, Arnd Bergmann
  Cc: Ulf Hansson, Kai-Heng Feng, Linux Kernel Mailing List,
	Linux Next Mailing List, linux-mmc

Hi all,

After merging the char-misc tree, today's linux-next build (x86
allmodconfig) failed like this:

/tmp/next/build/drivers/mmc/host/rtsx_pci_sdmmc.c: In function 'sd_request':
/tmp/next/build/drivers/mmc/host/rtsx_pci_sdmmc.c:809:17: error: unused variable 'dev' [-Werror=unused-variable]
  809 |  struct device *dev = &host->pdev->dev;
      |                 ^~~
/tmp/next/build/drivers/mmc/host/rtsx_pci_sdmmc.c: In function 'sdmmc_set_ios':
/tmp/next/build/drivers/mmc/host/rtsx_pci_sdmmc.c:1084:17: error: unused variable 'dev' [-Werror=unused-variable]
 1084 |  struct device *dev = &host->pdev->dev;
      |                 ^~~
/tmp/next/build/drivers/mmc/host/rtsx_pci_sdmmc.c: In function 'sdmmc_get_ro':
/tmp/next/build/drivers/mmc/host/rtsx_pci_sdmmc.c:1133:17: error: unused variable 'dev' [-Werror=unused-variable]
 1133 |  struct device *dev = &host->pdev->dev;
      |                 ^~~
/tmp/next/build/drivers/mmc/host/rtsx_pci_sdmmc.c: In function 'sdmmc_get_cd':
/tmp/next/build/drivers/mmc/host/rtsx_pci_sdmmc.c:1159:17: error: unused variable 'dev' [-Werror=unused-variable]
 1159 |  struct device *dev = &host->pdev->dev;
      |                 ^~~
/tmp/next/build/drivers/mmc/host/rtsx_pci_sdmmc.c: In function 'sdmmc_switch_voltage':
/tmp/next/build/drivers/mmc/host/rtsx_pci_sdmmc.c:1258:17: error: unused variable 'dev' [-Werror=unused-variable]
 1258 |  struct device *dev = &host->pdev->dev;
      |                 ^~~
/tmp/next/build/drivers/mmc/host/rtsx_pci_sdmmc.c: In function 'sdmmc_execute_tuning':
/tmp/next/build/drivers/mmc/host/rtsx_pci_sdmmc.c:1311:17: error: unused variable 'dev' [-Werror=unused-variable]
 1311 |  struct device *dev = &host->pdev->dev;
      |                 ^~~
cc1: all warnings being treated as errors

Caused by commit

  7570fb41e450ba37 ("mmc: rtsx: Let MMC core handle runtime PM")

I have used the char-misc tree from yesterday instead.

^ permalink raw reply	[flat|nested] 51+ messages in thread
* linux-next: build failure after merge of the char-misc tree
@ 2021-10-27  4:48 Stephen Rothwell
  2021-10-27  6:51 ` Greg KH
  0 siblings, 1 reply; 51+ messages in thread
From: Stephen Rothwell @ 2021-10-27  4:48 UTC (permalink / raw)
  To: Greg KH, Arnd Bergmann; +Cc: Linux Kernel Mailing List, Linux Next Mailing List

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

Hi all,

After merging the char-misc tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:

ERROR: modpost: module drm_shmem_helper uses symbol dma_buf_vunmap from namespace DMA_BUF, but does not import it.
ERROR: modpost: module drm_shmem_helper uses symbol dma_buf_mmap from namespace DMA_BUF, but does not import it.
ERROR: modpost: module drm_shmem_helper uses symbol dma_buf_vmap from namespace DMA_BUF, but does not import it.

Caused by commit

  16b0314aa746 ("dma-buf: move dma-buf symbols into the DMA_BUF module namespace")

I have applied the following patch for today.

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Wed, 27 Oct 2021 15:44:18 +1100
Subject: [PATCH] fix for "dma-buf: move dma-buf symbols into the DMA_BUF
 module namespace"

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 drivers/gpu/drm/drm_gem_shmem_helper.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/gpu/drm/drm_gem_shmem_helper.c b/drivers/gpu/drm/drm_gem_shmem_helper.c
index 57ceecb3f4d8..f7324582afe7 100644
--- a/drivers/gpu/drm/drm_gem_shmem_helper.c
+++ b/drivers/gpu/drm/drm_gem_shmem_helper.c
@@ -22,6 +22,8 @@
 #include <drm/drm_prime.h>
 #include <drm/drm_print.h>
 
+MODULE_IMPORT_NS(DMA_BUF);
+
 /**
  * DOC: overview
  *
-- 
2.33.0

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply related	[flat|nested] 51+ messages in thread
* linux-next: build failure after merge of the char-misc tree
@ 2020-05-04  1:46 Stephen Rothwell
  2020-05-04  1:47 ` Stephen Rothwell
  0 siblings, 1 reply; 51+ messages in thread
From: Stephen Rothwell @ 2020-05-04  1:46 UTC (permalink / raw)
  To: Greg KH, Arnd Bergmann
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Rajan Vaja,
	Jolly Shah

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

Hi all,

After merging the char-misc tree, Friday's linux-next build (arm64
allmodconfig) failed like this:

ERROR: modpost: "zynqmp_pm_fpga_get_status" [drivers/fpga/zynqmp-fpga.ko] undefined!
ERROR: modpost: "zynqmp_pm_fpga_load" [drivers/fpga/zynqmp-fpga.ko] undefined!

Presumably caused by commit

  4db8180ffe7c ("firmware: xilinx: Remove eemi ops for fpga related APIs")

Reported-by: "kernelci.org bot" <bot@kernelci.org>

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 51+ messages in thread
* linux-next: build failure after merge of the char-misc tree
@ 2019-07-08  9:23 Stephen Rothwell
  2019-07-12  0:44 ` Stephen Rothwell
  0 siblings, 1 reply; 51+ messages in thread
From: Stephen Rothwell @ 2019-07-08  9:23 UTC (permalink / raw)
  To: Greg KH, Arnd Bergmann, Al Viro
  Cc: Linux Next Mailing List, Linux Kernel Mailing List,
	David Howells, Nadav Amit

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

Hi all,

After merging the char-misc tree, today's linux-next build (x86_64
allmodconfig) failed like this:

drivers/misc/vmw_balloon.c: In function 'vmballoon_mount':
drivers/misc/vmw_balloon.c:1736:14: error: 'simple_dname' undeclared (first use in this function); did you mean 'simple_rename'?
   .d_dname = simple_dname,
              ^~~~~~~~~~~~
              simple_rename
drivers/misc/vmw_balloon.c:1736:14: note: each undeclared identifier is reported only once for each function it appears in
drivers/misc/vmw_balloon.c:1739:9: error: implicit declaration of function 'mount_pseudo'; did you mean 'mount_bdev'? [-Werror=implicit-function-declaration]
  return mount_pseudo(fs_type, "balloon-vmware:", NULL, &ops,
         ^~~~~~~~~~~~
         mount_bdev
drivers/misc/vmw_balloon.c:1739:9: warning: returning 'int' from a function with return type 'struct dentry *' makes pointer from integer without a cast [-Wint-conversion]
  return mount_pseudo(fs_type, "balloon-vmware:", NULL, &ops,
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        BALLOON_VMW_MAGIC);
        ~~~~~~~~~~~~~~~~~~

Caused by commit

  83a8afa72e9c ("vmw_balloon: Compaction support")

interacting with commits

  7e5f7bb08b8c ("unexport simple_dname()")
  8d9e46d80777 ("fold mount_pseudo_xattr() into pseudo_fs_get_tree()")

from the vfs tree.

I applied the following merge fix patch:

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Mon, 8 Jul 2019 19:17:56 +1000
Subject: [PATCH] convert vmwballoon to use the new mount API

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 drivers/misc/vmw_balloon.c | 14 ++++----------
 1 file changed, 4 insertions(+), 10 deletions(-)

diff --git a/drivers/misc/vmw_balloon.c b/drivers/misc/vmw_balloon.c
index 91fa43051535..e8c0f7525f13 100644
--- a/drivers/misc/vmw_balloon.c
+++ b/drivers/misc/vmw_balloon.c
@@ -29,6 +29,7 @@
 #include <linux/slab.h>
 #include <linux/spinlock.h>
 #include <linux/mount.h>
+#include <linux/pseudo_fs.h>
 #include <linux/balloon_compaction.h>
 #include <linux/vmw_vmci_defs.h>
 #include <linux/vmw_vmci_api.h>
@@ -1728,21 +1729,14 @@ static inline void vmballoon_debugfs_exit(struct vmballoon *b)
 
 #ifdef CONFIG_BALLOON_COMPACTION
 
-static struct dentry *vmballoon_mount(struct file_system_type *fs_type,
-				      int flags, const char *dev_name,
-				      void *data)
+static int vmballoon_init_fs_context(struct fs_context *fc)
 {
-	static const struct dentry_operations ops = {
-		.d_dname = simple_dname,
-	};
-
-	return mount_pseudo(fs_type, "balloon-vmware:", NULL, &ops,
-			    BALLOON_VMW_MAGIC);
+	return init_pseudo(fc, BALLOON_VMW_MAGIC) ? 0 : -ENOMEM;
 }
 
 static struct file_system_type vmballoon_fs = {
 	.name           = "balloon-vmware",
-	.mount          = vmballoon_mount,
+	.init_fs_context          = vmballoon_init_fs_context,
 	.kill_sb        = kill_anon_super,
 };
 
-- 
2.20.1

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply related	[flat|nested] 51+ messages in thread
* linux-next: build failure after merge of the char-misc tree
@ 2017-04-12  5:18 Stephen Rothwell
  2017-04-12 10:33 ` Greg KH
  0 siblings, 1 reply; 51+ messages in thread
From: Stephen Rothwell @ 2017-04-12  5:18 UTC (permalink / raw)
  To: Greg KH, Arnd Bergmann, Thomas Gleixner, Ingo Molnar,
	H. Peter Anvin, Peter Zijlstra
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List, Thierry Escande

Hi all,

After merging the char-misc tree, today's linux-next build (x86_64
allmodconfig) failed like this:

In file included from drivers/firmware/google/memconsole-x86-legacy.c:23:0:
arch/x86/include/uapi/asm/e820.h:66:23: error: 'E820_X_MAX' undeclared here (not in a function)
  struct e820entry map[E820_X_MAX];
                       ^

Caused by commit

  afe9dba4f9ae ("firmware: google memconsole: Move specific EBDA parts")

interacting with commit

  66441bd3cfdc ("x86/boot/e820: Move asm/e820.h to asm/e820/api.h")

from the tip tree.

I applied the following merge fix patch:

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Wed, 12 Apr 2017 15:12:12 +1000
Subject: [PATCH] firmware: google memconsole: merge fix for e820.h move

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 drivers/firmware/google/memconsole-x86-legacy.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/firmware/google/memconsole-x86-legacy.c b/drivers/firmware/google/memconsole-x86-legacy.c
index 529078c62488..99df2749c4c5 100644
--- a/drivers/firmware/google/memconsole-x86-legacy.c
+++ b/drivers/firmware/google/memconsole-x86-legacy.c
@@ -20,7 +20,7 @@
 #include <linux/dmi.h>
 #include <linux/mm.h>
 #include <asm/bios_ebda.h>
-#include <asm/e820.h>
+#include <asm/e820/api.h>
 #include <linux/acpi.h>
 
 #include "memconsole.h"
-- 
2.11.0

-- 
Cheers,
Stephen Rothwell

^ permalink raw reply related	[flat|nested] 51+ messages in thread
* linux-next: build failure after merge of the char-misc tree
@ 2017-03-20  2:44 Stephen Rothwell
  2017-03-20 12:23 ` Arnd Bergmann
  0 siblings, 1 reply; 51+ messages in thread
From: Stephen Rothwell @ 2017-03-20  2:44 UTC (permalink / raw)
  To: Greg KH, Arnd Bergmann
  Cc: linux-next, linux-kernel, Cyril Bur, Joel Stanley,
	Benjamin Herrenschmidt

Hi all,

After merging the char-misc tree, today's linux-next build (x86_64
allmodconfig) failed like this:

drivers/misc/aspeed-lpc-ctrl.c: In function 'aspeed_lpc_ctrl_mmap':
drivers/misc/aspeed-lpc-ctrl.c:51:9: error: implicit declaration of function 'pgprot_dmacoherent' [-Werror=implicit-function-declaration]
  prot = pgprot_dmacoherent(prot);
         ^
drivers/misc/aspeed-lpc-ctrl.c:51:7: error: incompatible types when assigning to type 'pgprot_t {aka struct pgprot}' from type 'int'
  prot = pgprot_dmacoherent(prot);
       ^
In file included from include/linux/miscdevice.h:6:0,
                 from drivers/misc/aspeed-lpc-ctrl.c:11:
drivers/misc/aspeed-lpc-ctrl.c: In function 'aspeed_lpc_ctrl_probe':
drivers/misc/aspeed-lpc-ctrl.c:232:17: warning: format '%x' expects argument of type 'unsigned int', but argument 3 has type 'phys_addr_t {aka long long unsigned int}' [-Wformat=]
   dev_info(dev, "Loaded at 0x%08x (0x%08x)\n",
                 ^
include/linux/device.h:1317:51: note: in definition of macro 'dev_info'
 #define dev_info(dev, fmt, arg...) _dev_info(dev, fmt, ##arg)
                                                   ^
drivers/misc/aspeed-lpc-ctrl.c:232:17: warning: format '%x' expects argument of type 'unsigned int', but argument 4 has type 'resource_size_t {aka long long unsigned int}' [-Wformat=]
   dev_info(dev, "Loaded at 0x%08x (0x%08x)\n",
                 ^
include/linux/device.h:1317:51: note: in definition of macro 'dev_info'
 #define dev_info(dev, fmt, arg...) _dev_info(dev, fmt, ##arg)
                                                   ^

Caused by commit

  6c4e97678501 ("drivers/misc: Add Aspeed LPC control driver")

Clearly this will only build on arm :-(  You can only use COMPILE_TEST
if you can reasonably expect the build to work on all architectures
and platforms.

I have added the following patch for today (the warnings should be fixed as well):

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Mon, 20 Mar 2017 13:38:10 +1100
Subject: [PATCH] drivers/misc: Aspeed LPC control driver will only build on arm

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 drivers/misc/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
index fb933b0b9297..52a46b129214 100644
--- a/drivers/misc/Kconfig
+++ b/drivers/misc/Kconfig
@@ -773,7 +773,7 @@ config PANEL_BOOT_MESSAGE
 endif # PANEL
 
 config ASPEED_LPC_CTRL
-	depends on (ARCH_ASPEED || COMPILE_TEST) && REGMAP && MFD_SYSCON
+	depends on ARCH_ASPEED && REGMAP && MFD_SYSCON
 	tristate "Aspeed ast2400/2500 HOST LPC to BMC bridge control"
 	---help---
 	  Control Aspeed ast2400/2500 HOST LPC to BMC mappings through
-- 
2.11.0

-- 
Cheers,
Stephen Rothwell

^ permalink raw reply related	[flat|nested] 51+ messages in thread
* linux-next: build failure after merge of the char-misc tree
@ 2015-08-07  6:32 Stephen Rothwell
  0 siblings, 0 replies; 51+ messages in thread
From: Stephen Rothwell @ 2015-08-07  6:32 UTC (permalink / raw)
  To: Greg KH, Arnd Bergmann, Thomas Gleixner, Ingo Molnar,
	H. Peter Anvin, Peter Zijlstra
  Cc: linux-next, linux-kernel, K. Y. Srinivasan, Andy Lutomirski

Hi all,

After merging the char-misc tree, today's linux-next build (x86_64
allmodconfig) failed like this:

drivers/hv/hv.c: In function 'read_hv_clock_tsc':
drivers/hv/hv.c:154:4: error: implicit declaration of function 'rdtscll' [-Werror=implicit-function-declaration]
    rdtscll(cur_tsc);
    ^

Caused by commit

  ca9357bd26c2 ("Drivers: hv: vmbus: Implement a clocksource based on the TSC page")

interacting with commits

  87be28aaf145 ("x86/asm/tsc: Replace rdtscll() with native_read_tsc()")
  4ea1636b04db ("x86/asm/tsc: Rename native_read_tsc() to rdtsc()")

from the tip tree.

Please consider maintaining API's for a release cycle when changing them.

I have applied the following merge fix patch:

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Fri, 7 Aug 2015 16:21:32 +1000
Subject: [PATCH] Drivers: hv: vmbus: fix for the removal of rdtscll()

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 drivers/hv/hv.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/hv/hv.c b/drivers/hv/hv.c
index 6341be8739ae..335064f01c37 100644
--- a/drivers/hv/hv.c
+++ b/drivers/hv/hv.c
@@ -151,7 +151,7 @@ static cycle_t read_hv_clock_tsc(struct clocksource *arg)
 			u64 scale = tsc_pg->tsc_scale;
 			s64 offset = tsc_pg->tsc_offset;
 
-			rdtscll(cur_tsc);
+			cur_tsc = rdtsc();
 			/* current_tick = ((cur_tsc *scale) >> 64) + offset */
 			asm("mulq %3"
 				: "=d" (current_tick), "=a" (tmp)
-- 
2.5.0

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

^ permalink raw reply related	[flat|nested] 51+ messages in thread
* linux-next: build failure after merge of the char-misc tree
@ 2015-05-27  5:52 Stephen Rothwell
  2015-05-27  7:08 ` Winkler, Tomas
  0 siblings, 1 reply; 51+ messages in thread
From: Stephen Rothwell @ 2015-05-27  5:52 UTC (permalink / raw)
  To: Greg KH, Arnd Bergmann; +Cc: linux-next, linux-kernel, Tomas Winkler

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

Hi all,

After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig)
failed like this:

drivers/nfc/microread/mei.c:70:2: error: implicit declaration of function '__UUID_LE' [-Werror=implicit-function-declaration]
  { MICROREAD_DRIVER_NAME, MEI_NFC_UUID},
  ^
drivers/nfc/microread/mei.c:70:2: warning: missing braces around initializer [-Wmissing-braces]
drivers/nfc/microread/mei.c:70:2: warning: (near initialization for 'microread_mei_tbl[0].uuid') [-Wmissing-braces]
drivers/nfc/microread/mei.c:70:2: error: initializer element is not constant
drivers/nfc/microread/mei.c:70:2: error: (near initialization for 'microread_mei_tbl[0].uuid[0]')
cc1: some warnings being treated as errors

Caused by commit c93b76b34b4d ("mei: bus: report also uuid in module
alias").

I have used the char-misc tree from next-20150526 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

^ permalink raw reply	[flat|nested] 51+ messages in thread
* linux-next: build failure after merge of the char-misc tree
@ 2014-02-21  5:47 Stephen Rothwell
  2014-02-26  6:47 ` Stephen Rothwell
  0 siblings, 1 reply; 51+ messages in thread
From: Stephen Rothwell @ 2014-02-21  5:47 UTC (permalink / raw)
  To: Greg KH, Arnd Bergmann; +Cc: linux-next, linux-kernel, Bjorn Helgaas

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

Hi all,

After merging the char-misc tree, today's linux-next build (x86_64
allmodconfig) failed like this:

In file included from drivers/misc/mei/hw-txe.c:25:0:
drivers/misc/mei/hw-txe.h:63:1: error: unknown type name 'irqreturn_t'
 irqreturn_t mei_txe_irq_quick_handler(int irq, void *dev_id);
 ^
drivers/misc/mei/hw-txe.h:64:1: error: unknown type name 'irqreturn_t'
 irqreturn_t mei_txe_irq_thread_handler(int irq, void *dev_id);
 ^
drivers/misc/mei/hw-txe.c:879:1: error: unknown type name 'irqreturn_t'
 irqreturn_t mei_txe_irq_quick_handler(int irq, void *dev_id)
 ^
drivers/misc/mei/hw-txe.c: In function 'mei_txe_irq_quick_handler':
drivers/misc/mei/hw-txe.c:884:10: error: 'IRQ_WAKE_THREAD' undeclared (first use in this function)
   return IRQ_WAKE_THREAD;
          ^
drivers/misc/mei/hw-txe.c:884:10: note: each undeclared identifier is reported only once for each function it appears in
drivers/misc/mei/hw-txe.c:885:9: error: 'IRQ_NONE' undeclared (first use in this function)
  return IRQ_NONE;
         ^
drivers/misc/mei/hw-txe.c: At top level:
drivers/misc/mei/hw-txe.c:898:1: error: unknown type name 'irqreturn_t'
 irqreturn_t mei_txe_irq_thread_handler(int irq, void *dev_id)
 ^
drivers/misc/mei/hw-txe.c: In function 'mei_txe_irq_thread_handler':
drivers/misc/mei/hw-txe.c:1007:9: error: 'IRQ_HANDLED' undeclared (first use in this function)
  return IRQ_HANDLED;
         ^
drivers/misc/mei/hw-txe.c: In function 'mei_txe_irq_quick_handler':
drivers/misc/mei/hw-txe.c:886:1: warning: control reaches end of non-void function [-Wreturn-type]
 }
 ^
drivers/misc/mei/hw-txe.c: In function 'mei_txe_irq_thread_handler':
drivers/misc/mei/hw-txe.c:1008:1: warning: control reaches end of non-void function [-Wreturn-type]
 }
 ^

Caused by commit 266f6178d1f1 ("mei: txe: add hw-txe.h header file") but
probably exposed by commit 46cb7b1bd86f ("PCI: Remove unused SR-IOV VF
Migration support") from the pci tree which removed the include of
irqreturn.h from pci.h ...

See Rule 1 from Documentation/SubmitChecklist ...

I added the following merge fix patch (this should be applied to the
char-misc tree):

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Fri, 21 Feb 2014 16:38:28 +1100
Subject: [PATCH] mei: txe: include irqreturn.h for irqreturn_t etc

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 drivers/misc/mei/hw-txe.c | 1 +
 drivers/misc/mei/hw-txe.h | 2 ++
 2 files changed, 3 insertions(+)

diff --git a/drivers/misc/mei/hw-txe.c b/drivers/misc/mei/hw-txe.c
index 19579e560dad..49a5ed376969 100644
--- a/drivers/misc/mei/hw-txe.c
+++ b/drivers/misc/mei/hw-txe.c
@@ -18,6 +18,7 @@
 #include <linux/jiffies.h>
 #include <linux/delay.h>
 #include <linux/kthread.h>
+#include <linux/irqreturn.h>
 
 #include <linux/mei.h>
 
diff --git a/drivers/misc/mei/hw-txe.h b/drivers/misc/mei/hw-txe.h
index 857d88ccef61..fdb665f44d5d 100644
--- a/drivers/misc/mei/hw-txe.h
+++ b/drivers/misc/mei/hw-txe.h
@@ -17,6 +17,8 @@
 #ifndef _MEI_HW_TXE_H_
 #define _MEI_HW_TXE_H_
 
+#include <linux/irqreturn.h>
+
 #include "hw.h"
 #include "hw-txe-regs.h"
 
-- 
1.9.0

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply related	[flat|nested] 51+ messages in thread
* linux-next: build failure after merge of the char-misc tree
@ 2013-09-27  7:10 Stephen Rothwell
  2013-09-28  1:04 ` Greg KH
  0 siblings, 1 reply; 51+ messages in thread
From: Stephen Rothwell @ 2013-09-27  7:10 UTC (permalink / raw)
  To: Greg KH, Arnd Bergmann
  Cc: linux-next, linux-kernel, Tejun Heo, Sudeep Dutt,
	Dasaratharaman Chandramouli, Ashutosh Dixit, Caz Yokoyama,
	Harshavardhan R Kharche, Nikhil Rao

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

Hi all,

After merging the char-misc tree, today's linux-next build (x86_64
allmodconfig) failed like this:

drivers/misc/mic/host/mic_main.c: In function 'mic_probe':
drivers/misc/mic/host/mic_main.c:320:3: error: too many arguments to function 'sysfs_get_dirent'
   NULL, "state");
   ^
In file included from include/linux/kobject.h:21:0,
                 from include/linux/module.h:16,
                 from drivers/misc/mic/host/mic_main.c:26:
include/linux/sysfs.h:465:1: note: declared here
 sysfs_get_dirent(struct sysfs_dirent *parent_sd, const unsigned char *name)
 ^

Caused by commit 3a6a9201897c ("Intel MIC Host Driver, card OS state
management") interacting with commit 388975cccaaf ("sysfs: clean up
sysfs_get_dirent()") from the driver-core tree.

I added this merge fix patch:

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Fri, 27 Sep 2013 17:07:12 +1000
Subject: [PATCH] Intel MIC Host Driver: fix for sysfs_get_dirent API change

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 drivers/misc/mic/host/mic_main.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/drivers/misc/mic/host/mic_main.c b/drivers/misc/mic/host/mic_main.c
index a8965d4..28c8490 100644
--- a/drivers/misc/mic/host/mic_main.c
+++ b/drivers/misc/mic/host/mic_main.c
@@ -316,8 +316,7 @@ static int mic_probe(struct pci_dev *pdev,
 			"device_create_with_groups failed rc %d\n", rc);
 		goto smpt_uninit;
 	}
-	mdev->state_sysfs = sysfs_get_dirent(mdev->sdev->kobj.sd,
-		NULL, "state");
+	mdev->state_sysfs = sysfs_get_dirent(mdev->sdev->kobj.sd, "state");
 	if (!mdev->state_sysfs) {
 		rc = -ENODEV;
 		dev_err(&pdev->dev, "sysfs_get_dirent failed rc %d\n", rc);
-- 
1.8.4.rc3


-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply related	[flat|nested] 51+ messages in thread
* linux-next: build failure after merge of the char-misc tree
@ 2013-04-02  6:29 Stephen Rothwell
  2013-04-02  6:49 ` Richard Weinberger
  0 siblings, 1 reply; 51+ messages in thread
From: Stephen Rothwell @ 2013-04-02  6:29 UTC (permalink / raw)
  To: Greg KH, Arnd Bergmann; +Cc: linux-next, linux-kernel, Richard Weinberger

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

Hi all,

After merging the char-misc tree, today's linux-next build (x86_64
allmodconfig) failed like this:

drivers/misc/cs5535-mfgpt.c:30:3: warning: missing terminating " character [enabled by default]
drivers/misc/cs5535-mfgpt.c:31:31: warning: missing terminating " character [enabled by default]
drivers/misc/cs5535-mfgpt.c:384:0: error: unterminated argument list invoking macro "MODULE_PARM_DESC"
drivers/misc/cs5535-mfgpt.c:27:1: error: expected '=', ',', ';', 'asm' or '__attribute__' at end of input

Caused by commit 945480b159aa ("cs5535-mfgpt: Add another reset method").

I have used the char-misc tree from next-20130328 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au


[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply	[flat|nested] 51+ messages in thread
* linux-next: build failure after merge of the char-misc tree
@ 2013-03-26  4:18 Stephen Rothwell
  0 siblings, 0 replies; 51+ messages in thread
From: Stephen Rothwell @ 2013-03-26  4:18 UTC (permalink / raw)
  To: Greg KH, Arnd Bergmann
  Cc: linux-next, linux-kernel, Kenneth Heitke, David Brown

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

Hi all,

After merging the char-misc tree, today's linux-next build
(x86_64_allmodconfig) failed like this:

drivers/input/keyboard/pmic8xxx-keypad.c:24:35: fatal error: linux/mfd/pm8xxx/gpio.h: No such file or directory

Caused by commit e44b0ceee4cc ("add single-wire serial bus interface
(SSBI) driver") which added the Kconfig symbol MSM_SSBI (later changed to
just SSBI) which did not exist in the tree before.  However,
MFD_PM8921_CORE depended on it and that selects MFD_PM8XXX which allows
the above file to build (and fail).

I have used the char-misc tree from next-20130325 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply	[flat|nested] 51+ messages in thread
* linux-next: build failure after merge of the char-misc tree
@ 2013-03-18  2:56 Stephen Rothwell
  2013-03-18  8:58 ` Kurt Van Dijck
  0 siblings, 1 reply; 51+ messages in thread
From: Stephen Rothwell @ 2013-03-18  2:56 UTC (permalink / raw)
  To: Greg KH, Arnd Bergmann; +Cc: linux-next, linux-kernel, Kurt Van Dijck

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

Hi all,

After merging the char-misc tree, today's linux-next build (x86_64
allmodconfig) failed like this:

drivers/net/can/softing/softing_cs.c:343:1: error: expected identifier or '(' before '&' token
drivers/net/can/softing/softing_cs.c: In function '__inittest':
drivers/net/can/softing/softing_cs.c:343:1: error: 'softingcs_driver_init' undeclared (first use in this function)
drivers/net/can/softing/softing_cs.c:343:1: note: each undeclared identifier is reported only once for each function it appears in
drivers/net/can/softing/softing_cs.c: At top level:
drivers/net/can/softing/softing_cs.c:343:1: error: expected identifier or '(' before '&' token
drivers/net/can/softing/softing_cs.c: In function '__exittest':
drivers/net/can/softing/softing_cs.c:343:1: error: 'softingcs_driver_exit' undeclared (first use in this function)
drivers/net/can/softing/softing_cs.c: At top level:
drivers/net/can/softing/softing_cs.c:335:29: warning: 'softingcs_driver' defined but not used [-Wunused-variable]
drivers/net/can/softing/softing_cs.c:343:1: error: 'init_module' aliased to undefined symbol '&softingcs_driver_init'
drivers/net/can/softing/softing_cs.c:343:1: error: 'cleanup_module' aliased to undefined symbol '&softingcs_driver_exit'

Caused by commit a750fa4edd9e ("softingcs: use module_pcmcia_driver").

I have used the char-misc tree form next-20130315 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

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

end of thread, other threads:[~2023-06-26  9:09 UTC | newest]

Thread overview: 51+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-27  8:08 linux-next: build failure after merge of the char-misc tree Stephen Rothwell
2020-07-27  9:24 ` Greg KH
2020-07-27  9:28   ` Oded Gabbay
2020-07-27 10:05     ` Greg KH
2020-07-27 10:59       ` Oded Gabbay
2020-07-28  7:33   ` Stephen Rothwell
2020-07-28  7:53     ` Greg KH
2020-07-28  8:23       ` Stephen Rothwell
2020-07-28 17:17         ` Greg KH
2020-07-28 17:19           ` Greg KH
2020-07-29  9:55             ` Oded Gabbay
  -- strict thread matches above, loose matches on Subject: below --
2023-06-26  4:25 Stephen Rothwell
2023-06-26  9:06 ` Greg KH
2022-05-20  9:46 Stephen Rothwell
2022-05-20 19:08 ` Greg KH
2022-06-12 17:23   ` Samuel Thibault
2022-02-25 20:40 broonie
2022-02-26 15:08 ` Greg KH
2022-03-01  5:14   ` Stephen Rothwell
2022-03-01 21:27     ` Greg KH
2021-10-27  4:48 Stephen Rothwell
2021-10-27  6:51 ` Greg KH
2020-05-04  1:46 Stephen Rothwell
2020-05-04  1:47 ` Stephen Rothwell
2020-05-04  7:14   ` Greg KH
     [not found]   ` <BYAPR02MB394115C2C80B1169D282A646B7A60@BYAPR02MB3941.namprd02.prod.outlook.com>
2020-05-04  7:31     ` Greg KH
2019-07-08  9:23 Stephen Rothwell
2019-07-12  0:44 ` Stephen Rothwell
2019-07-12  7:59   ` Greg KH
2017-04-12  5:18 Stephen Rothwell
2017-04-12 10:33 ` Greg KH
2017-03-20  2:44 Stephen Rothwell
2017-03-20 12:23 ` Arnd Bergmann
2017-03-21  0:18   ` Benjamin Herrenschmidt
2017-03-21  0:36     ` Cyril Bur
2017-03-21  2:58       ` Joel Stanley
2015-08-07  6:32 Stephen Rothwell
2015-05-27  5:52 Stephen Rothwell
2015-05-27  7:08 ` Winkler, Tomas
2015-05-27 12:36   ` Greg KH
2014-02-21  5:47 Stephen Rothwell
2014-02-26  6:47 ` Stephen Rothwell
2014-02-27  3:37   ` Greg KH
2014-02-27  5:48     ` Stephen Rothwell
2013-09-27  7:10 Stephen Rothwell
2013-09-28  1:04 ` Greg KH
2013-04-02  6:29 Stephen Rothwell
2013-04-02  6:49 ` Richard Weinberger
2013-03-26  4:18 Stephen Rothwell
2013-03-18  2:56 Stephen Rothwell
2013-03-18  8:58 ` Kurt Van Dijck

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).