From: Greg KH <greg@kroah.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: netdev@vger.kernel.org, gwingerde@gmail.com,
larry.finger@lwfinger.net, davem@davemloft.net,
bhutchings@solarflare.com, arnd@arndb.de,
linux-kernel@vger.kernel.org,
Fabio Estevam <fabio.estevam@freescale.com>
Subject: Re: [PATCH] drivers: misc: Remove MISC_DEVICES config option
Date: Thu, 5 Jan 2012 14:39:33 -0800 [thread overview]
Message-ID: <20120105223933.GA10268@kroah.com> (raw)
In-Reply-To: <1325796541-11402-1-git-send-email-festevam@gmail.com>
On Thu, Jan 05, 2012 at 06:49:01PM -0200, Fabio Estevam wrote:
> MISC_DEVICES option alone does not select any kernel code and can cause dependency build warnings, such as:
>
> warning: (KS8851 && AX88796_93CX6 && RTL8180 && RTL8187 && ADM8211 && RT2400PCI && RT2500PCI && RT61PCI && RT2800PCI && R8187SE) selects EEPROM_93CX6 which has unmet direct dependencies (MISC_DEVICES)
>
> Remove MISC_DEVICES option so that any dependency on this symbol is avoided.
Are you sure that this isn't getting confused with the
drivers/char/misc.c interface instead of the "throw a bunch of randome
drivers into drivers/misc/" issue?
Why would anything ever want to select MISC_DEVICES? What happens if
you just remove that select line from the Kconfig?
thanks,
greg k-h
next prev parent reply other threads:[~2012-01-05 22:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 20:49 [PATCH] drivers: misc: Remove MISC_DEVICES config option Fabio Estevam
2012-01-05 22:39 ` Greg KH [this message]
2012-01-06 1:18 ` Fabio Estevam
2012-01-06 5:03 ` Greg KH
2012-01-06 12:00 ` Arnd Bergmann
2012-01-24 2:57 ` Fabio Estevam
2012-01-24 3:03 ` Greg KH
2012-01-24 3:17 ` Fabio Estevam
2012-01-24 3:48 ` Greg KH
2012-01-24 12:25 ` Arnd Bergmann
2012-01-05 23:45 ` Randy Dunlap
2012-01-05 23:42 ` Larry Finger
2012-01-06 0:08 ` Larry Finger
2012-01-06 1:13 ` Fabio Estevam
2012-01-24 4:11 ` [PATCH v2] " Fabio Estevam
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=20120105223933.GA10268@kroah.com \
--to=greg@kroah.com \
--cc=arnd@arndb.de \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=gwingerde@gmail.com \
--cc=larry.finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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.