Re: linux-next: build warnings after merge of the drm tree
On Tue, Dec 15, 2020 at 3:47 AM Stephen Rothwell wrote:
>
> Hi all,
>
> On Tue, 15 Dec 2020 06:50:45 +1100 Stephen Rothwell
> wrote:
> >
> > On Mon, 16 Nov 2020 10:44:44 +1100 Stephen Rothwell
> > wrote:
> > >
> > > On Thu, 5 Nov 2020 17:50:31 +1100 Stephen Rothwell
> > > wrote:
> > > >
> > > > After merging the drm tree, today's linux-next build (htmldocs) produced
> > > > these warnings:
> > > >
> > > > include/linux/dma-buf-map.h:106: warning: Excess function parameter
> > > > 'vaddr' description in 'DMA_BUF_MAP_INIT_VADDR'
> > > > include/linux/dma-buf-map.h:106: warning: Function parameter or member
> > > > 'vaddr_' not described in 'DMA_BUF_MAP_INIT_VADDR'
> > > > include/linux/dma-buf-map.h:106: warning: Excess function parameter
> > > > 'vaddr' description in 'DMA_BUF_MAP_INIT_VADDR'
> > > >
> > > > Introduced by commit
> > > >
> > > > 20e76f1a7059 ("dma-buf: Use struct dma_buf_map in dma_buf_vunmap()
> > > > interfaces")
> > >
> > > I am still getting these warnings.
> >
> > I am still getting these warnings.
>
> These warnings are now from Linus' tree.
We had a stuck pull request which should have been included in the
main merge pull. This should be fixed now in drm-next. Well in a few
minutes when the compile testing is done.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
Re: linux-next: build warnings after merge of the drm tree
Hi all,
On Tue, 15 Dec 2020 06:50:45 +1100 Stephen Rothwell
wrote:
>
> On Mon, 16 Nov 2020 10:44:44 +1100 Stephen Rothwell
> wrote:
> >
> > On Thu, 5 Nov 2020 17:50:31 +1100 Stephen Rothwell
> > wrote:
> > >
> > > After merging the drm tree, today's linux-next build (htmldocs) produced
> > > these warnings:
> > >
> > > include/linux/dma-buf-map.h:106: warning: Excess function parameter
> > > 'vaddr' description in 'DMA_BUF_MAP_INIT_VADDR'
> > > include/linux/dma-buf-map.h:106: warning: Function parameter or member
> > > 'vaddr_' not described in 'DMA_BUF_MAP_INIT_VADDR'
> > > include/linux/dma-buf-map.h:106: warning: Excess function parameter
> > > 'vaddr' description in 'DMA_BUF_MAP_INIT_VADDR'
> > >
> > > Introduced by commit
> > >
> > > 20e76f1a7059 ("dma-buf: Use struct dma_buf_map in dma_buf_vunmap()
> > > interfaces")
> >
> > I am still getting these warnings.
>
> I am still getting these warnings.
These warnings are now from Linus' tree.
--
Cheers,
Stephen Rothwell
pgpm9DmJ3exXo.pgp
Description: OpenPGP digital signature
Re: linux-next: build warnings after merge of the drm tree
Hi all,
On Mon, 16 Nov 2020 10:44:44 +1100 Stephen Rothwell
wrote:
>
> On Thu, 5 Nov 2020 17:50:31 +1100 Stephen Rothwell
> wrote:
> >
> > After merging the drm tree, today's linux-next build (htmldocs) produced
> > these warnings:
> >
> > include/linux/dma-buf-map.h:106: warning: Excess function parameter 'vaddr'
> > description in 'DMA_BUF_MAP_INIT_VADDR'
> > include/linux/dma-buf-map.h:106: warning: Function parameter or member
> > 'vaddr_' not described in 'DMA_BUF_MAP_INIT_VADDR'
> > include/linux/dma-buf-map.h:106: warning: Excess function parameter 'vaddr'
> > description in 'DMA_BUF_MAP_INIT_VADDR'
> >
> > Introduced by commit
> >
> > 20e76f1a7059 ("dma-buf: Use struct dma_buf_map in dma_buf_vunmap()
> > interfaces")
>
> I am still getting these warnings.
I am still getting these warnings.
--
Cheers,
Stephen Rothwell
pgpCrKX8kpDey.pgp
Description: OpenPGP digital signature
Re: linux-next: build warnings after merge of the drm tree
Hi all,
On Thu, 5 Nov 2020 17:50:31 +1100 Stephen Rothwell
wrote:
>
> Hi all,
>
> After merging the drm tree, today's linux-next build (htmldocs) produced
> these warnings:
>
> include/linux/dma-buf-map.h:106: warning: Excess function parameter 'vaddr'
> description in 'DMA_BUF_MAP_INIT_VADDR'
> include/linux/dma-buf-map.h:106: warning: Function parameter or member
> 'vaddr_' not described in 'DMA_BUF_MAP_INIT_VADDR'
> include/linux/dma-buf-map.h:106: warning: Excess function parameter 'vaddr'
> description in 'DMA_BUF_MAP_INIT_VADDR'
>
> Introduced by commit
>
> 20e76f1a7059 ("dma-buf: Use struct dma_buf_map in dma_buf_vunmap()
> interfaces")
I am still getting these warnings.
--
Cheers,
Stephen Rothwell
pgpF6NG4pE7C4.pgp
Description: OpenPGP digital signature
Re: linux-next: build warnings after merge of the drm tree
Hi Stephen,
On Wed, 1 Nov 2017 14:16:40 +1100
Stephen Rothwell wrote:
> Hi Dave,
>
> After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
> produced these warnings:
>
> drivers/gpu/drm/vc4/vc4_bo.c: In function 'vc4_bo_stats_debugfs':
> drivers/gpu/drm/vc4/vc4_bo.c:91:17: warning: format '%d' expects argument of
> type 'int', but argument 4 has type 'size_t {aka long unsigned int}'
> [-Wformat=]
>seq_printf(m, "%30s: %6dkb BOs (%d)\n", "userspace BO cache",
> ^
> drivers/gpu/drm/vc4/vc4_bo.c:95:17: warning: format '%d' expects argument of
> type 'int', but argument 4 has type 'size_t {aka long unsigned int}'
> [-Wformat=]
>seq_printf(m, "%30s: %6dkb BOs (%d)\n", "total purged BO",
> ^
>
> Introduced by commit
>
> b9f19259b84d ("drm/vc4: Add the DRM_IOCTL_VC4_GEM_MADVISE ioctl")
>
Just sent a patch fixing the problem.
Thanks for the report.
Boris
Re: linux-next: build warnings after merge of the drm tree
Hi Eric, On Fri, 02 Jun 2017 17:45:10 -0700 Eric Anholt wrote: > > Stephen Rothwell writes: > > > On Fri, 02 Jun 2017 14:05:14 -0700 Eric Anholt wrote: > >> > >> Not sure what's going on. I see your "yesterday" list present, and not > >> your "today" commit. > > > > I just refetched the drm-misc tree and received no changes. It is > > still as I said in the previous email. This tree is fetched from the > > drm-misc-next branch of git://anongit.freedesktop.org/drm/drm-misc > > > > The single commit currently in that branch was authored by "Caesar Wang > > " and committed by "Mark Yao > > " (both now cc'd). > > I see that commit in drm-misc-next-fixes, but not drm-misc-next. I see it in the drm-misc-fixes tree (branch for-linux-next-fixes) as well (along with another commit). I made a mistake above, the drm-misc tree is branch for-linux-next. -- Cheers, Stephen Rothwell
Re: linux-next: build warnings after merge of the drm tree
Stephen Rothwell writes: > Hi Eric, > > On Fri, 02 Jun 2017 14:05:14 -0700 Eric Anholt wrote: >> >> Not sure what's going on. I see your "yesterday" list present, and not >> your "today" commit. > > I just refetched the drm-misc tree and received no changes. It is > still as I said in the previous email. This tree is fetched from the > drm-misc-next branch of git://anongit.freedesktop.org/drm/drm-misc > > The single commit currently in that branch was authored by "Caesar Wang > " and committed by "Mark Yao > " (both now cc'd). I see that commit in drm-misc-next-fixes, but not drm-misc-next. signature.asc Description: PGP signature
Re: linux-next: build warnings after merge of the drm tree
Hi Eric, On Fri, 02 Jun 2017 14:05:14 -0700 Eric Anholt wrote: > > Not sure what's going on. I see your "yesterday" list present, and not > your "today" commit. I just refetched the drm-misc tree and received no changes. It is still as I said in the previous email. This tree is fetched from the drm-misc-next branch of git://anongit.freedesktop.org/drm/drm-misc The single commit currently in that branch was authored by "Caesar Wang " and committed by "Mark Yao " (both now cc'd). -- Cheers, Stephen Rothwell
Re: linux-next: build warnings after merge of the drm tree
Stephen Rothwell writes:
> Hi all,
>
> On Thu, 25 May 2017 11:49:42 +1000 Stephen Rothwell
> wrote:
>>
>> On Fri, 19 May 2017 10:49:06 -0700 Eric Anholt wrote:
>> >
>> > Stephen Rothwell writes:
>> >
>> > > After merging the drm tree, today's linux-next build (x86_64
>> > > allmodconfig)
>> > > produced these warnings:
>> > >
>> > > drivers/gpu/drm/pl111/pl111_drv.c:81:12: warning: 'pl111_modeset_init'
>> > > defined but not used [-Wunused-function]
>> > > static int pl111_modeset_init(struct drm_device *dev)
>> > > ^
>> > > drivers/gpu/drm/pl111/pl111_drv.c:149:26: warning: 'pl111_drm_driver'
>> > > defined but not used [-Wunused-variable]
>> > > static struct drm_driver pl111_drm_driver = {
>> > > ^
>> >
>> > Sorry about that -- I thought that kbuild test robot would give me
>> > notification of new warnings.
>> >
>> > Patch incoming.
>>
>> I saw the patch, but it doesn't seem to have been applied anywhere yet.
>
> So these warnings went away yesterday, but are back today after quite a
> few patches were dropped from the drm-misc tree.
>
> Yesterday it contained theses (relative to the drm tree):
>
> 9a8d5e4a53dc drm/vc4: Fix comment in vc4_drv.h
> 66d6dd45eee2 drm/pl111: fix warnings without CONFIG_ARM_AMBA
> 91110a4b64fe drm/atomic: Consitfy mode parameter to
> drm_atomic_set_mode_for_crtc()
> fb51cbfd4b2e drm/arcgpu: Drop drm_vblank_cleanup
> e3ec0e1e38a5 drm/atmel: Drop drm_vblank_cleanup
> 85769cf7cd7f drm/imx: Drop drm_vblank_cleanup
> a360b39b5137 drm/meson: Drop drm_vblank_cleanup
> 25b905fe4323 drm/stm: Drop drm_vblank_cleanup
> d79373bd4d7e drm/sun4i: Drop drm_vblank_cleanup
> 8938d13585bc drm: better document how to send out the crtc disable event
> 46466b0dac3f drm: Use vsnprintf extension %ph
> 99cdb35e787b drm/doc: move printf helpers out of drmP.h
> e7cc23de3e4e drm/pl111: select DRM_PANEL
> 7dbcbce9f551 drm/bridge: analogix-anx78xx: Use bridge->mode_valid() callback
> faf94a0883ce drm: Use mode_valid() in atomic modeset
> 97f973d65260 drm: Use new mode_valid() helpers in connector probe helper
> b1240f81a186 drm: Introduce drm_bridge_mode_valid()
> da251bf8f935 drm: Add drm_{crtc/encoder/connector}_mode_valid()
> 18e51064c42c drm: Remove drm_device->virtdev
> a301b1118615 drm: todo: remove task about switch to drm_connector_list_iter
> eb53a46be597 drm: remove unsafe drm_for_each_connector()
> 4894bf711d19 drm/vc4: use drm_for_each_connector_iter()
> 875dd62697fe drm/nouveau: use drm_for_each_connector_iter()
> c8bf8b968adb drm/mediatek: use drm_for_each_connector_iter()
> 2fd96b4116bf drm/i915: use drm_for_each_connector_iter()
> 2cbeb64f6c70 drm/rockchip: use drm_for_each_connector_iter()
> 48a92916729b drm/exynos: use drm_for_each_connector_iter()
>
> Today it only has:
>
> 2d7b56378d32 drm/rockchip: gem: add the lacks lock and trivial changes
Not sure what's going on. I see your "yesterday" list present, and not
your "today" commit.
signature.asc
Description: PGP signature
Re: linux-next: build warnings after merge of the drm tree
Hi all,
On Thu, 25 May 2017 11:49:42 +1000 Stephen Rothwell
wrote:
>
> On Fri, 19 May 2017 10:49:06 -0700 Eric Anholt wrote:
> >
> > Stephen Rothwell writes:
> >
> > > After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
> > > produced these warnings:
> > >
> > > drivers/gpu/drm/pl111/pl111_drv.c:81:12: warning: 'pl111_modeset_init'
> > > defined but not used [-Wunused-function]
> > > static int pl111_modeset_init(struct drm_device *dev)
> > > ^
> > > drivers/gpu/drm/pl111/pl111_drv.c:149:26: warning: 'pl111_drm_driver'
> > > defined but not used [-Wunused-variable]
> > > static struct drm_driver pl111_drm_driver = {
> > > ^
> >
> > Sorry about that -- I thought that kbuild test robot would give me
> > notification of new warnings.
> >
> > Patch incoming.
>
> I saw the patch, but it doesn't seem to have been applied anywhere yet.
So these warnings went away yesterday, but are back today after quite a
few patches were dropped from the drm-misc tree.
Yesterday it contained theses (relative to the drm tree):
9a8d5e4a53dc drm/vc4: Fix comment in vc4_drv.h
66d6dd45eee2 drm/pl111: fix warnings without CONFIG_ARM_AMBA
91110a4b64fe drm/atomic: Consitfy mode parameter to
drm_atomic_set_mode_for_crtc()
fb51cbfd4b2e drm/arcgpu: Drop drm_vblank_cleanup
e3ec0e1e38a5 drm/atmel: Drop drm_vblank_cleanup
85769cf7cd7f drm/imx: Drop drm_vblank_cleanup
a360b39b5137 drm/meson: Drop drm_vblank_cleanup
25b905fe4323 drm/stm: Drop drm_vblank_cleanup
d79373bd4d7e drm/sun4i: Drop drm_vblank_cleanup
8938d13585bc drm: better document how to send out the crtc disable event
46466b0dac3f drm: Use vsnprintf extension %ph
99cdb35e787b drm/doc: move printf helpers out of drmP.h
e7cc23de3e4e drm/pl111: select DRM_PANEL
7dbcbce9f551 drm/bridge: analogix-anx78xx: Use bridge->mode_valid() callback
faf94a0883ce drm: Use mode_valid() in atomic modeset
97f973d65260 drm: Use new mode_valid() helpers in connector probe helper
b1240f81a186 drm: Introduce drm_bridge_mode_valid()
da251bf8f935 drm: Add drm_{crtc/encoder/connector}_mode_valid()
18e51064c42c drm: Remove drm_device->virtdev
a301b1118615 drm: todo: remove task about switch to drm_connector_list_iter
eb53a46be597 drm: remove unsafe drm_for_each_connector()
4894bf711d19 drm/vc4: use drm_for_each_connector_iter()
875dd62697fe drm/nouveau: use drm_for_each_connector_iter()
c8bf8b968adb drm/mediatek: use drm_for_each_connector_iter()
2fd96b4116bf drm/i915: use drm_for_each_connector_iter()
2cbeb64f6c70 drm/rockchip: use drm_for_each_connector_iter()
48a92916729b drm/exynos: use drm_for_each_connector_iter()
Today it only has:
2d7b56378d32 drm/rockchip: gem: add the lacks lock and trivial changes
--
Cheers,
Stephen Rothwell
Re: linux-next: build warnings after merge of the drm tree
Hi Eric,
On Fri, 19 May 2017 10:49:06 -0700 Eric Anholt wrote:
>
> Stephen Rothwell writes:
>
> > After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
> > produced these warnings:
> >
> > drivers/gpu/drm/pl111/pl111_drv.c:81:12: warning: 'pl111_modeset_init'
> > defined but not used [-Wunused-function]
> > static int pl111_modeset_init(struct drm_device *dev)
> > ^
> > drivers/gpu/drm/pl111/pl111_drv.c:149:26: warning: 'pl111_drm_driver'
> > defined but not used [-Wunused-variable]
> > static struct drm_driver pl111_drm_driver = {
> > ^
>
> Sorry about that -- I thought that kbuild test robot would give me
> notification of new warnings.
>
> Patch incoming.
I saw the patch, but it doesn't seem to have been applied anywhere yet.
--
Cheers,
Stephen Rothwell
Re: linux-next: build warnings after merge of the drm tree
Stephen Rothwell writes:
> Hi Dave,
>
> After merging the drm tree, today's linux-next build (x86_64 allmodconfig)
> produced these warnings:
>
> drivers/gpu/drm/pl111/pl111_drv.c:81:12: warning: 'pl111_modeset_init'
> defined but not used [-Wunused-function]
> static int pl111_modeset_init(struct drm_device *dev)
> ^
> drivers/gpu/drm/pl111/pl111_drv.c:149:26: warning: 'pl111_drm_driver' defined
> but not used [-Wunused-variable]
> static struct drm_driver pl111_drm_driver = {
> ^
Sorry about that -- I thought that kbuild test robot would give me
notification of new warnings.
Patch incoming.
signature.asc
Description: PGP signature
Re: linux-next: build warnings after merge of the drm tree
On Tue, Sep 4, 2012 at 10:22 AM, Dave Airlie wrote:
>> > After merging the drm tree, today's linux-next build (powerpc
>> > ppc64_defconfig) produced these warnings:
>> >
>> > drivers/gpu/drm/udl/Kconfig:1:error: recursive dependency detected!
>> > drivers/gpu/drm/udl/Kconfig:1: symbol DRM_UDL depends on USB_ARCH_HAS_HCD
>> > drivers/usb/Kconfig:76: symbol USB_ARCH_HAS_HCD depends on USB_SUPPORT
>> > drivers/usb/Kconfig:58: symbol USB_SUPPORT is selected by DRM_USB
>> > drivers/gpu/drm/Kconfig:22: symbol DRM_USB is selected by DRM_UDL
>> > warning: (PPC_PS3) selects USB_OHCI_LITTLE_ENDIAN which has unmet direct
>> > dependencies (USB_SUPPORT && USB_OHCI_HCD)
>> > warning: (PPC_PS3 && PPC_CELLEB) selects USB_OHCI_BIG_ENDIAN_MMIO which
>> > has unmet direct dependencies (USB_SUPPORT && USB_OHCI_HCD)
>> > warning: (PPC_PS3 && PPC_CELLEB && USB_EHCI_HCD_PMC_MSP &&
>> > XPS_USB_HCD_XILINX && USB_OCTEON_EHCI) selects USB_EHCI_BIG_ENDIAN_MMIO
>> > which has unmet direct dependencies (USB_SUPPORT && USB_EHCI_HCD &&
>> > (PPC_CELLEB || PPC_PS3 || 440EPX || ARCH_IXP4XX || XPS_USB_HCD_XILINX ||
>> > PPC_MPC512x || CPU_CAVIUM_OCTEON || PMC_MSP || SPARC_LEON || MIPS_SEAD3))
>> >
>> > The x86_64 allmodconfig produces these:
>> >
>> > drivers/gpu/drm/udl/Kconfig:1:error: recursive dependency detected!
>> > drivers/gpu/drm/udl/Kconfig:1: symbol DRM_UDL depends on USB_ARCH_HAS_HCD
>> > drivers/usb/Kconfig:76: symbol USB_ARCH_HAS_HCD depends on USB_SUPPORT
>> > drivers/usb/Kconfig:58: symbol USB_SUPPORT is selected by DRM_USB
>> > drivers/gpu/drm/Kconfig:22: symbol DRM_USB is selected by DRM_UDL
>> > warning: (MOUSE_APPLETOUCH && MOUSE_BCM5974 && MOUSE_SYNAPTICS_USB &&
>> > JOYSTICK_XPAD && TABLET_USB_ACECAD && TABLET_USB_AIPTEK &&
>> > TABLET_USB_HANWANG && TABLET_USB_KBTAB && TABLET_USB_WACOM &&
>> > TOUCHSCREEN_USB_COMPOSITE && INPUT_ATI_REMOTE2 && INPUT_KEYSPAN_REMOTE &&
>> > INPUT_POWERMATE && INPUT_YEALINK && INPUT_CM109 && RC_ATI_REMOTE &&
>> > IR_IMON && IR_MCEUSB && IR_REDRAT3 && IR_STREAMZAP && IR_IGUANA &&
>> > IR_TTUSBIR && DRM_USB) selects USB which has unmet direct dependencies
>> > (USB_SUPPORT && USB_ARCH_HAS_HCD)
>> >
>> > Maybe introduced by commit df0b34430072 ("drm/usb: select USB_SUPPORT in
>> > Kconfig"), maybe interacting with a commit 8f057d7bca54 ("gpu/mfd/usb:
>> > Fix USB randconfig problems") from Linus' tree (that added "depends on
>> > USB_ARCH_HAS_HCD" to "config DRM_USB" and "config DRM_UDL").
>> >
>> > I have left this mess for now, but it needs addressing.
>>
>> I have sent a fix ("drm/udl: usb: Fix recursive Kconfig dependency")
>> for this mess and pinged airlied on IRC.
>> NOTE: I saw this when I merged drm(-intel){-fixes,next} into next-20120824.
>
> I[ve pushed it to drm-next now hopefully it will resolve the mess.
>
Great and thanks!
Can't say if the label of my patch should be changed to "drm/usb: ..."
as the culprit commit df0b34430072 (drm/usb: select USB_SUPPORT in
Kconfig) has it and the fix is done in drm/usb Kconfig definition.
( Thinking loud of people searching within (git-)logs. )
For me the current status of drm-next is OK (next time I do better).
- Sedat -
[1]
http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commitdiff;h=df0b344300724e00db9fff7eb6406eb91f450b91
> thanks,
> Dave.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: build warnings after merge of the drm tree
> > After merging the drm tree, today's linux-next build (powerpc
> > ppc64_defconfig) produced these warnings:
> >
> > drivers/gpu/drm/udl/Kconfig:1:error: recursive dependency detected!
> > drivers/gpu/drm/udl/Kconfig:1: symbol DRM_UDL depends on USB_ARCH_HAS_HCD
> > drivers/usb/Kconfig:76: symbol USB_ARCH_HAS_HCD depends on USB_SUPPORT
> > drivers/usb/Kconfig:58: symbol USB_SUPPORT is selected by DRM_USB
> > drivers/gpu/drm/Kconfig:22: symbol DRM_USB is selected by DRM_UDL
> > warning: (PPC_PS3) selects USB_OHCI_LITTLE_ENDIAN which has unmet direct
> > dependencies (USB_SUPPORT && USB_OHCI_HCD)
> > warning: (PPC_PS3 && PPC_CELLEB) selects USB_OHCI_BIG_ENDIAN_MMIO which has
> > unmet direct dependencies (USB_SUPPORT && USB_OHCI_HCD)
> > warning: (PPC_PS3 && PPC_CELLEB && USB_EHCI_HCD_PMC_MSP &&
> > XPS_USB_HCD_XILINX && USB_OCTEON_EHCI) selects USB_EHCI_BIG_ENDIAN_MMIO
> > which has unmet direct dependencies (USB_SUPPORT && USB_EHCI_HCD &&
> > (PPC_CELLEB || PPC_PS3 || 440EPX || ARCH_IXP4XX || XPS_USB_HCD_XILINX ||
> > PPC_MPC512x || CPU_CAVIUM_OCTEON || PMC_MSP || SPARC_LEON || MIPS_SEAD3))
> >
> > The x86_64 allmodconfig produces these:
> >
> > drivers/gpu/drm/udl/Kconfig:1:error: recursive dependency detected!
> > drivers/gpu/drm/udl/Kconfig:1: symbol DRM_UDL depends on USB_ARCH_HAS_HCD
> > drivers/usb/Kconfig:76: symbol USB_ARCH_HAS_HCD depends on USB_SUPPORT
> > drivers/usb/Kconfig:58: symbol USB_SUPPORT is selected by DRM_USB
> > drivers/gpu/drm/Kconfig:22: symbol DRM_USB is selected by DRM_UDL
> > warning: (MOUSE_APPLETOUCH && MOUSE_BCM5974 && MOUSE_SYNAPTICS_USB &&
> > JOYSTICK_XPAD && TABLET_USB_ACECAD && TABLET_USB_AIPTEK &&
> > TABLET_USB_HANWANG && TABLET_USB_KBTAB && TABLET_USB_WACOM &&
> > TOUCHSCREEN_USB_COMPOSITE && INPUT_ATI_REMOTE2 && INPUT_KEYSPAN_REMOTE &&
> > INPUT_POWERMATE && INPUT_YEALINK && INPUT_CM109 && RC_ATI_REMOTE && IR_IMON
> > && IR_MCEUSB && IR_REDRAT3 && IR_STREAMZAP && IR_IGUANA && IR_TTUSBIR &&
> > DRM_USB) selects USB which has unmet direct dependencies (USB_SUPPORT &&
> > USB_ARCH_HAS_HCD)
> >
> > Maybe introduced by commit df0b34430072 ("drm/usb: select USB_SUPPORT in
> > Kconfig"), maybe interacting with a commit 8f057d7bca54 ("gpu/mfd/usb:
> > Fix USB randconfig problems") from Linus' tree (that added "depends on
> > USB_ARCH_HAS_HCD" to "config DRM_USB" and "config DRM_UDL").
> >
> > I have left this mess for now, but it needs addressing.
>
> I have sent a fix ("drm/udl: usb: Fix recursive Kconfig dependency")
> for this mess and pinged airlied on IRC.
> NOTE: I saw this when I merged drm(-intel){-fixes,next} into next-20120824.
I[ve pushed it to drm-next now hopefully it will resolve the mess.
thanks,
Dave.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: build warnings after merge of the drm tree
On Tue, Sep 4, 2012 at 5:58 AM, Stephen Rothwell wrote:
> Hi Dave,
>
> After merging the drm tree, today's linux-next build (powerpc
> ppc64_defconfig) produced these warnings:
>
> drivers/gpu/drm/udl/Kconfig:1:error: recursive dependency detected!
> drivers/gpu/drm/udl/Kconfig:1: symbol DRM_UDL depends on USB_ARCH_HAS_HCD
> drivers/usb/Kconfig:76: symbol USB_ARCH_HAS_HCD depends on USB_SUPPORT
> drivers/usb/Kconfig:58: symbol USB_SUPPORT is selected by DRM_USB
> drivers/gpu/drm/Kconfig:22: symbol DRM_USB is selected by DRM_UDL
> warning: (PPC_PS3) selects USB_OHCI_LITTLE_ENDIAN which has unmet direct
> dependencies (USB_SUPPORT && USB_OHCI_HCD)
> warning: (PPC_PS3 && PPC_CELLEB) selects USB_OHCI_BIG_ENDIAN_MMIO which has
> unmet direct dependencies (USB_SUPPORT && USB_OHCI_HCD)
> warning: (PPC_PS3 && PPC_CELLEB && USB_EHCI_HCD_PMC_MSP && XPS_USB_HCD_XILINX
> && USB_OCTEON_EHCI) selects USB_EHCI_BIG_ENDIAN_MMIO which has unmet direct
> dependencies (USB_SUPPORT && USB_EHCI_HCD && (PPC_CELLEB || PPC_PS3 || 440EPX
> || ARCH_IXP4XX || XPS_USB_HCD_XILINX || PPC_MPC512x || CPU_CAVIUM_OCTEON ||
> PMC_MSP || SPARC_LEON || MIPS_SEAD3))
>
> The x86_64 allmodconfig produces these:
>
> drivers/gpu/drm/udl/Kconfig:1:error: recursive dependency detected!
> drivers/gpu/drm/udl/Kconfig:1: symbol DRM_UDL depends on USB_ARCH_HAS_HCD
> drivers/usb/Kconfig:76: symbol USB_ARCH_HAS_HCD depends on USB_SUPPORT
> drivers/usb/Kconfig:58: symbol USB_SUPPORT is selected by DRM_USB
> drivers/gpu/drm/Kconfig:22: symbol DRM_USB is selected by DRM_UDL
> warning: (MOUSE_APPLETOUCH && MOUSE_BCM5974 && MOUSE_SYNAPTICS_USB &&
> JOYSTICK_XPAD && TABLET_USB_ACECAD && TABLET_USB_AIPTEK && TABLET_USB_HANWANG
> && TABLET_USB_KBTAB && TABLET_USB_WACOM && TOUCHSCREEN_USB_COMPOSITE &&
> INPUT_ATI_REMOTE2 && INPUT_KEYSPAN_REMOTE && INPUT_POWERMATE && INPUT_YEALINK
> && INPUT_CM109 && RC_ATI_REMOTE && IR_IMON && IR_MCEUSB && IR_REDRAT3 &&
> IR_STREAMZAP && IR_IGUANA && IR_TTUSBIR && DRM_USB) selects USB which has
> unmet direct dependencies (USB_SUPPORT && USB_ARCH_HAS_HCD)
>
> Maybe introduced by commit df0b34430072 ("drm/usb: select USB_SUPPORT in
> Kconfig"), maybe interacting with a commit 8f057d7bca54 ("gpu/mfd/usb:
> Fix USB randconfig problems") from Linus' tree (that added "depends on
> USB_ARCH_HAS_HCD" to "config DRM_USB" and "config DRM_UDL").
>
> I have left this mess for now, but it needs addressing.
I have sent a fix ("drm/udl: usb: Fix recursive Kconfig dependency")
for this mess and pinged airlied on IRC.
NOTE: I saw this when I merged drm(-intel){-fixes,next} into next-20120824.
- Sedat -
[1] https://patchwork.kernel.org/patch/1373391/
> --
> Cheers,
> Stephen Rothwells...@canb.auug.org.au
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: build warnings after merge of the drm tree
On Tue, Sep 04, 2012 at 01:58:29PM +1000, Stephen Rothwell wrote:
> Hi Dave,
>
> After merging the drm tree, today's linux-next build (powerpc
> ppc64_defconfig) produced these warnings:
>
> drivers/gpu/drm/udl/Kconfig:1:error: recursive dependency detected!
> drivers/gpu/drm/udl/Kconfig:1:symbol DRM_UDL depends on
> USB_ARCH_HAS_HCD
> drivers/usb/Kconfig:76: symbol USB_ARCH_HAS_HCD depends on USB_SUPPORT
> drivers/usb/Kconfig:58: symbol USB_SUPPORT is selected by DRM_USB
> drivers/gpu/drm/Kconfig:22: symbol DRM_USB is selected by DRM_UDL
> warning: (PPC_PS3) selects USB_OHCI_LITTLE_ENDIAN which has unmet direct
> dependencies (USB_SUPPORT && USB_OHCI_HCD)
> warning: (PPC_PS3 && PPC_CELLEB) selects USB_OHCI_BIG_ENDIAN_MMIO which has
> unmet direct dependencies (USB_SUPPORT && USB_OHCI_HCD)
> warning: (PPC_PS3 && PPC_CELLEB && USB_EHCI_HCD_PMC_MSP && XPS_USB_HCD_XILINX
> && USB_OCTEON_EHCI) selects USB_EHCI_BIG_ENDIAN_MMIO which has unmet direct
> dependencies (USB_SUPPORT && USB_EHCI_HCD && (PPC_CELLEB || PPC_PS3 || 440EPX
> || ARCH_IXP4XX || XPS_USB_HCD_XILINX || PPC_MPC512x || CPU_CAVIUM_OCTEON ||
> PMC_MSP || SPARC_LEON || MIPS_SEAD3))
>
> The x86_64 allmodconfig produces these:
>
> drivers/gpu/drm/udl/Kconfig:1:error: recursive dependency detected!
> drivers/gpu/drm/udl/Kconfig:1:symbol DRM_UDL depends on
> USB_ARCH_HAS_HCD
> drivers/usb/Kconfig:76: symbol USB_ARCH_HAS_HCD depends on USB_SUPPORT
> drivers/usb/Kconfig:58: symbol USB_SUPPORT is selected by DRM_USB
> drivers/gpu/drm/Kconfig:22: symbol DRM_USB is selected by DRM_UDL
> warning: (MOUSE_APPLETOUCH && MOUSE_BCM5974 && MOUSE_SYNAPTICS_USB &&
> JOYSTICK_XPAD && TABLET_USB_ACECAD && TABLET_USB_AIPTEK && TABLET_USB_HANWANG
> && TABLET_USB_KBTAB && TABLET_USB_WACOM && TOUCHSCREEN_USB_COMPOSITE &&
> INPUT_ATI_REMOTE2 && INPUT_KEYSPAN_REMOTE && INPUT_POWERMATE && INPUT_YEALINK
> && INPUT_CM109 && RC_ATI_REMOTE && IR_IMON && IR_MCEUSB && IR_REDRAT3 &&
> IR_STREAMZAP && IR_IGUANA && IR_TTUSBIR && DRM_USB) selects USB which has
> unmet direct dependencies (USB_SUPPORT && USB_ARCH_HAS_HCD)
>
> Maybe introduced by commit df0b34430072 ("drm/usb: select USB_SUPPORT in
> Kconfig"), maybe interacting with a commit 8f057d7bca54 ("gpu/mfd/usb:
> Fix USB randconfig problems") from Linus' tree (that added "depends on
> USB_ARCH_HAS_HCD" to "config DRM_USB" and "config DRM_UDL").
>
Looks like it. I'll have a look once the tree is available.
Guenter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
