From: Larry Finger <Larry.Finger@lwfinger.net>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Fabio Estevam <festevam@gmail.com>,
netdev@vger.kernel.org, gwingerde@gmail.com, davem@davemloft.net,
bhutchings@solarflare.com, greg@kroah.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, 05 Jan 2012 17:42:54 -0600 [thread overview]
Message-ID: <4F06357E.8050000@lwfinger.net> (raw)
In-Reply-To: <4F0635FE.6050507@xenotime.net>
On 01/05/2012 05:45 PM, Randy Dunlap wrote:
> On 01/05/2012 12:49 PM, 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.
>
> I thought that one purpose of MISC_DEVICES was to allow anyone to disable all
> options under it with one click (or keystroke), but since several drivers now
> "select MISC_DEVICES", that does not work.
>
> I would like to be able to disable all MISC_DEVICES, but since that
> does not currently function, this change is OK with me.
All of the drivers in the above list select *only* one driver in the
MISC_DEVICES category. If that one were moved outside of MISC_DEVICES, most, if
not all,problems would go away.
Larry
next prev parent reply other threads:[~2012-01-05 23:43 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
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 [this message]
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=4F06357E.8050000@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=arnd@arndb.de \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=greg@kroah.com \
--cc=gwingerde@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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