All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Kosina <jkosina@suse.cz>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
	Jan Beulich <jbeulich@suse.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: hid/Kconfig:7:error: recursive dependency detected!
Date: Tue, 3 Jul 2012 11:20:56 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.00.1207031120010.17304@pobox.suse.cz> (raw)
In-Reply-To: <20120703071102.GA5072@polaris.bitmath.org>

On Tue, 3 Jul 2012, Henrik Rydberg wrote:

> > > > I got this error while doing randconfig test:
> > > > 
> > > >         drivers/hid/Kconfig:7:error: recursive dependency detected!
> > > >         drivers/hid/Kconfig:7:  symbol HID is selected by USB_HID
> > > >         drivers/hid/usbhid/Kconfig:4:   symbol USB_HID depends on HID
> > > 
> > > What kernel tree does this apply to? Reading through the code again
> > > and testing your configuration, I cannot reproduce the
> > > problem. Indeed, in my tree, USB_HID does not depend on HID.
> > 
> > Henrik, I'm testing on today's linux-next.
> 
> Ah, yes, I see it. The problem is also present in Jiri's for-next
> tree. Jiri: the manual merge of drivers/hid/Kconfig seems to have gone
> wrong; in particular, the source of the usbhid config is inside the
> "if HID" statement, which creates the problem seen by Fengguang.

Indeed, I messed up the conflict resolution. I have pushed the new 
for-next branch with proper resolution now.

Thanks,

-- 
Jiri Kosina
SUSE Labs

      reply	other threads:[~2012-07-03  9:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03  4:06 hid/Kconfig:7:error: recursive dependency detected! Fengguang Wu
2012-07-03  6:44 ` Henrik Rydberg
2012-07-03  6:49   ` Fengguang Wu
2012-07-03  7:11     ` Henrik Rydberg
2012-07-03  9:20       ` Jiri Kosina [this message]

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=alpine.LNX.2.00.1207031120010.17304@pobox.suse.cz \
    --to=jkosina@suse.cz \
    --cc=fengguang.wu@intel.com \
    --cc=jbeulich@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rydberg@euromail.se \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.