From: Arnd Bergmann <arnd@arndb.de>
To: Greg KH <greg@kroah.com>
Cc: Fabio Estevam <festevam@gmail.com>,
netdev@vger.kernel.org, gwingerde@gmail.com,
larry.finger@lwfinger.net, davem@davemloft.net,
bhutchings@solarflare.com, linux-kernel@vger.kernel.org,
Fabio Estevam <fabio.estevam@freescale.com>
Subject: Re: [PATCH] drivers: misc: Remove MISC_DEVICES config option
Date: Fri, 6 Jan 2012 12:00:43 +0000 [thread overview]
Message-ID: <201201061200.44183.arnd@arndb.de> (raw)
In-Reply-To: <20120106050355.GA7633@kroah.com>
On Friday 06 January 2012, Greg KH wrote:
> On Thu, Jan 05, 2012 at 11:18:28PM -0200, Fabio Estevam wrote:
> > On Thu, Jan 5, 2012 at 8:39 PM, Greg KH <greg@kroah.com> wrote:
> >
> > > 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?
> >
> > Sorry, I am not aware of this issue.
> >
> > > Why would anything ever want to select MISC_DEVICES? What happens if
> > > you just remove that select line from the Kconfig?
> >
> > Yes, I don´t understand the point of allowing the selection MISC_DEVICES.
> >
> > IMHO it is potential for causing dependency issues.
>
> Then remove that selection. Nothing should be depending on a misc
> driver, if it is, then that implies that this is more than just a "misc"
> driver, and it should be moved elsewhere.
I think that is true for the majority of stuff we have under drivers/misc
anyway. I had done the same patch that Fabio sent a couple of months ago
but then forgot about it, so here is a wholehearted
Acked-by: Arnd Bergmann <arnd@arndb.de>
for the new patch. It fixes a real problem, and we applied a similar patch
in drivers/mfd as 8a0a8e8e already. We probably still want to find a better
home for drivers that frequently get selected by other subsystems as you
said, but that is an independent issue. I don't see why anyone would
need a way to disable all MISC drivers at once, when the only thing that
(in theory) connects them is that they are all different from everything
else.
Arnd
next prev parent reply other threads:[~2012-01-06 12:00 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 [this message]
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=201201061200.44183.arnd@arndb.de \
--to=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=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 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).