linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@gmail.com>
To: Dave Airlie <airlied@linux.ie>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Sachin Kamat <sachin.kamat@linaro.org>,
	Guenter Roeck <linux@roeck-us.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: linux-next: build warnings after merge of the drm tree
Date: Tue, 4 Sep 2012 10:58:36 +0200	[thread overview]
Message-ID: <CA+icZUWxfE6VqsRbFNNUhR_NStO9rPThv_h5wVirL4e+dKUmBQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1209040922110.523@skynet.skynet.ie>

On Tue, Sep 4, 2012 at 10:22 AM, Dave Airlie <airlied@linux.ie> 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.

  reply	other threads:[~2012-09-04  8:58 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-04  3:58 linux-next: build warnings after merge of the drm tree Stephen Rothwell
2012-09-04  5:31 ` Guenter Roeck
2012-09-04  6:40 ` Sedat Dilek
2012-09-04  8:22   ` Dave Airlie
2012-09-04  8:58     ` Sedat Dilek [this message]
2012-10-04  2:21 Stephen Rothwell
2017-02-19 23:48 Stephen Rothwell
2017-02-23 23:27 Stephen Rothwell
2017-05-19  2:07 Stephen Rothwell
2017-05-19 17:49 ` Eric Anholt
2017-05-25  1:49   ` Stephen Rothwell
2017-06-02  3:59     ` Stephen Rothwell
2017-06-02 21:05       ` Eric Anholt
2017-06-02 23:40         ` Stephen Rothwell
2017-06-03  0:45           ` Eric Anholt
2017-06-03  1:26             ` Stephen Rothwell
2017-11-01  3:16 Stephen Rothwell
2017-11-01  9:58 ` Boris Brezillon
2020-11-05  6:50 Stephen Rothwell
2020-11-15 23:44 ` Stephen Rothwell
2020-12-14 19:50   ` Stephen Rothwell
2020-12-15  2:47     ` Stephen Rothwell
2020-12-15  9:42       ` Daniel Vetter
2021-04-01  7:32 Stephen Rothwell
2021-04-21  6:30 ` Stephen Rothwell
2021-06-03  9:32 Stephen Rothwell
2021-07-08  2:20 ` Stephen Rothwell
2021-08-10  9:26   ` Stephen Rothwell
2021-08-10 10:14     ` Daniel Vetter
2021-08-10 10:38       ` Stephen Rothwell
2021-08-10 10:50         ` Daniel Vetter
2021-08-10 11:01           ` Stephen Rothwell
2021-08-10 12:39             ` Daniel Vetter
2021-08-10 13:21               ` Stephen Rothwell
2023-01-05  3:47 Stephen Rothwell
2023-06-13  6:29 Stephen Rothwell
2024-02-19  5:21 Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+icZUWxfE6VqsRbFNNUhR_NStO9rPThv_h5wVirL4e+dKUmBQ@mail.gmail.com \
    --to=sedat.dilek@gmail.com \
    --cc=airlied@linux.ie \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=sachin.kamat@linaro.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).