similar to: linux-next: Tree for Jul 21 (gpu/virtio)

Displaying 20 results from an estimated 10000 matches similar to: "linux-next: Tree for Jul 21 (gpu/virtio)"

2020 Nov 02
0
linux-next: Tree for Nov 2 [drivers/vdpa/vdpa_sim/vdpa_sim.ko]
On 11/1/20 9:28 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20201030: > on x86_64: when CONFIG_NET is not enabled: ERROR: modpost: "mac_pton" [drivers/vdpa/vdpa_sim/vdpa_sim.ko] undefined! Should VDPA_SIM, IFCVF, MLX5_VDPA_NET depend on NET or NETDEVICES? -- ~Randy Reported-by: Randy Dunlap <rdunlap at infradead.org>
2012 Oct 24
3
linux-next: Tree for Oct 24 (xen)
On 10/23/2012 09:19 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 201201023: > on x86_64: drivers/built-in.o: In function `dbgp_reset_prep': (.text+0xb96b5): undefined reference to `xen_dbgp_reset_prep' drivers/built-in.o: In function `dbgp_external_startup': (.text+0xb9d95): undefined reference to `xen_dbgp_external_startup' Full randconfig file is
2012 Oct 24
3
linux-next: Tree for Oct 24 (xen)
On 10/23/2012 09:19 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 201201023: > on x86_64: drivers/built-in.o: In function `dbgp_reset_prep': (.text+0xb96b5): undefined reference to `xen_dbgp_reset_prep' drivers/built-in.o: In function `dbgp_external_startup': (.text+0xb9d95): undefined reference to `xen_dbgp_external_startup' Full randconfig file is
2012 Oct 24
3
linux-next: Tree for Oct 24 (xen)
On 10/23/2012 09:19 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 201201023: > on x86_64: drivers/built-in.o: In function `dbgp_reset_prep': (.text+0xb96b5): undefined reference to `xen_dbgp_reset_prep' drivers/built-in.o: In function `dbgp_external_startup': (.text+0xb9d95): undefined reference to `xen_dbgp_external_startup' Full randconfig file is
2020 Aug 10
0
linux-next: Tree for Aug 10 (drivers/vdpa/mlx5/net)
On 8/9/20 9:10 PM, Stephen Rothwell wrote: > Hi all, > on i386: Lots (63) of left shift warnings: {not all are shown here} CC drivers/vdpa/mlx5/net/mlx5_vnet.o In file included from ../include/linux/bits.h:6:0, from ../include/linux/bitops.h:5, from ../include/linux/kernel.h:12, from ../include/linux/vdpa.h:5,
2016 Aug 02
1
[PATCH] drm/virtio: fix building without CONFIG_FBDEV
Removing the build-time dependency on DRM_KMS_FB_HELPER means we can now build with CONFIG_FB disabled or as a loadable module, leading to a link error: ERROR: "remove_conflicting_framebuffers" [drivers/gpu/drm/virtio/virtio-gpu.ko] undefined! There is no need to call remove_conflicting_framebuffers() if CONFIG_FB is disabled, or if the virtio-gpu driver is built-in and CONFIG_FB=m, as
2016 Aug 02
1
[PATCH] drm/virtio: fix building without CONFIG_FBDEV
Removing the build-time dependency on DRM_KMS_FB_HELPER means we can now build with CONFIG_FB disabled or as a loadable module, leading to a link error: ERROR: "remove_conflicting_framebuffers" [drivers/gpu/drm/virtio/virtio-gpu.ko] undefined! There is no need to call remove_conflicting_framebuffers() if CONFIG_FB is disabled, or if the virtio-gpu driver is built-in and CONFIG_FB=m, as
2020 Apr 16
0
linux-next: Tree for Apr 15 (vdpa)
On 2020/4/16 ??12:16, Randy Dunlap wrote: > On 4/14/20 10:22 PM, Stephen Rothwell wrote: >> Hi all, >> >> Changes since 20200414: >> > on x86_64: > > ERROR: modpost: "vringh_set_iotlb" [drivers/vdpa/vdpa_sim/vdpa_sim.ko] undefined! > ERROR: modpost: "vringh_init_iotlb" [drivers/vdpa/vdpa_sim/vdpa_sim.ko] undefined! > ERROR: modpost:
2018 Jan 07
2
[PATCH] virtio: make VIRTIO a menuconfig to ease disabling it all
No need to get into the submenu to disable all VIRTIO-related config entries. This makes it easier to disable all VIRTIO config options without entering the submenu. It will also enable one to see that en/dis-abled state from the outside menu. This is only intended to change menuconfig UI, not change the config dependencies. v2: Added "default y" to avoid breaking existing configs v3:
2013 Jun 26
1
linux-next: Tree for Jun 26 (xen/x86)
On 06/26/13 01:06, Stephen Rothwell wrote: > Hi all, > > Changes since 20130625: > CONFIG_SMP is not set CONFIG_X86_UP_APIC is not set on i386: drivers/built-in.o: In function `xen_callback_vector': (.text+0x1dc3cb): undefined reference to `first_system_vector' drivers/built-in.o: In function `xen_callback_vector': (.text+0x1dc3f5): undefined reference to
2013 Jun 26
1
linux-next: Tree for Jun 26 (xen/x86)
On 06/26/13 01:06, Stephen Rothwell wrote: > Hi all, > > Changes since 20130625: > CONFIG_SMP is not set CONFIG_X86_UP_APIC is not set on i386: drivers/built-in.o: In function `xen_callback_vector': (.text+0x1dc3cb): undefined reference to `first_system_vector' drivers/built-in.o: In function `xen_callback_vector': (.text+0x1dc3f5): undefined reference to
2013 Jun 26
1
linux-next: Tree for Jun 26 (xen/x86)
On 06/26/13 01:06, Stephen Rothwell wrote: > Hi all, > > Changes since 20130625: > CONFIG_SMP is not set CONFIG_X86_UP_APIC is not set on i386: drivers/built-in.o: In function `xen_callback_vector': (.text+0x1dc3cb): undefined reference to `first_system_vector' drivers/built-in.o: In function `xen_callback_vector': (.text+0x1dc3f5): undefined reference to
2011 Dec 19
1
linux-next: Tree for Dec 19 (xen)
On 12/18/2011 11:55 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20111216: drivers/xen/xenbus/xenbus_dev_frontend.c: In function 'xenbus_init': drivers/xen/xenbus/xenbus_dev_frontend.c:609:2: error: implicit declaration of function 'xen_domain' Full randconfig file is attached. -- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your
2011 Dec 19
1
linux-next: Tree for Dec 19 (xen)
On 12/18/2011 11:55 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20111216: drivers/xen/xenbus/xenbus_dev_frontend.c: In function 'xenbus_init': drivers/xen/xenbus/xenbus_dev_frontend.c:609:2: error: implicit declaration of function 'xen_domain' Full randconfig file is attached. -- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your
2018 Sep 01
0
[PATCH v3 04/13] fbdev: add remove_conflicting_pci_framebuffers()
Almost all PCI drivers using remove_conflicting_framebuffers() wrap it with the same code. --- v2: add kerneldoc for DRM helper v3: propagate remove_conflicting_framebuffers() return value + move kerneldoc to where function is implemented Signed-off-by: Micha? Miros?aw <mirq-linux at rere.qmqm.pl> --- drivers/video/fbdev/core/fbmem.c | 35 ++++++++++++++++++++++++++++++++
2017 Nov 24
0
[PATCH 02/13] fbdev: add remove_conflicting_pci_framebuffers()
Almost all drivers using remove_conflicting_framebuffers() wrap it with the same code. Extract common part from PCI drivers into separate remove_conflicting_pci_framebuffers(). Signed-off-by: Micha? Miros?aw <mirq-linux at rere.qmqm.pl> --- drivers/video/fbdev/core/fbmem.c | 22 ++++++++++++++++++++++ include/drm/drm_fb_helper.h | 12 ++++++++++++ include/linux/fb.h | 2
2011 Jun 15
0
linux-next: Tree for June 15 (xen)
On Wed, 15 Jun 2011 14:17:28 +1000 Stephen Rothwell wrote: > Hi all, > > Changes since 20110614: on x86_64: arch/x86/xen/mmu.c: In function 'xen_flush_tlb_others': arch/x86/xen/mmu.c:1234: error: 'num_processors' undeclared (first use in this function) kernel .config file is attached. (CONFIG_SMP is not enabled.) --- ~Randy *** Remember to use
2011 Jun 15
0
linux-next: Tree for June 15 (xen)
On Wed, 15 Jun 2011 14:17:28 +1000 Stephen Rothwell wrote: > Hi all, > > Changes since 20110614: on x86_64: arch/x86/xen/mmu.c: In function 'xen_flush_tlb_others': arch/x86/xen/mmu.c:1234: error: 'num_processors' undeclared (first use in this function) kernel .config file is attached. (CONFIG_SMP is not enabled.) --- ~Randy *** Remember to use
2011 Jun 15
0
linux-next: Tree for June 15 (xen)
On Wed, 15 Jun 2011 14:17:28 +1000 Stephen Rothwell wrote: > Hi all, > > Changes since 20110614: on x86_64: arch/x86/xen/mmu.c: In function 'xen_flush_tlb_others': arch/x86/xen/mmu.c:1234: error: 'num_processors' undeclared (first use in this function) kernel .config file is attached. (CONFIG_SMP is not enabled.) --- ~Randy *** Remember to use
2013 Jan 10
0
linux-next: Tree for Jan 10 (vmci)
On 01/10/13 11:17, Randy Dunlap wrote: > On 01/09/13 19:32, Stephen Rothwell wrote: >> Hi all, >> >> Changes since 20130109: >> > > > on i386, when CONFIG_PCI is not enabled: > > CC [M] drivers/misc/vmw_vmci/vmci_guest.o > drivers/misc/vmw_vmci/vmci_guest.c:58:20: error: array type has incomplete element type >