mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brent Casavant <bcasavan@sgi.com>
To: linux-kernel@vger.kernel.org
Cc: rubini@vision.unipv.it, oakad@yahoo.com, masbock@us.ibm.com,
	sascha@saschahauer.de, bunk@stusta.de, ankita@in.ibm.com
Subject: Kconfig include order of drivers/misc
Date: Mon, 9 Oct 2006 14:15:52 -0500 (CDT)	[thread overview]
Message-ID: <20061009140135.G64302@pkunk.americas.sgi.com> (raw)

Hello,

I am contemplating a patch which would move the drivers/sn/ioc4.c code
into drivers/misc, as the SGI IOC4 device may soon not be limited to
operation on the SGI SN2 platform.  However, to maintain proper Kconfig
dependency ordering, this will require me to move drivers/misc before
drivers/ide in the drivers/Kconfig file.

My examination of this change seems to indicate this should not cause
any problems for the drivers hosted under drivers/misc, however I wanted
to run it by those who have recently (i.e. since "git" began hosting
the Linux source) touched the drivers/misc/Kconfig file.

Do any of you anticipate a problem with the following change?

Thanks,
Brent

diff --git a/drivers/Kconfig b/drivers/Kconfig
index 263e86d..f394634 100644
--- a/drivers/Kconfig
+++ b/drivers/Kconfig
@@ -14,6 +14,10 @@ source "drivers/pnp/Kconfig"

 source "drivers/block/Kconfig"

+# misc before ide - BLK_DEV_SGIIOC4 depends on SGI_IOC4
+
+source "drivers/misc/Kconfig"
+
 source "drivers/ide/Kconfig"

 source "drivers/scsi/Kconfig"
@@ -52,8 +56,6 @@ source "drivers/w1/Kconfig"

 source "drivers/hwmon/Kconfig"

-source "drivers/misc/Kconfig"
-
 source "drivers/mfd/Kconfig"

 source "drivers/media/Kconfig"

-- 
Brent Casavant                          All music is folk music.  I ain't
bcasavan@sgi.com                        never heard a horse sing a song.
Silicon Graphics, Inc.                    -- Louis Armstrong

                 reply	other threads:[~2006-10-09 19:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20061009140135.G64302@pkunk.americas.sgi.com \
    --to=bcasavan@sgi.com \
    --cc=ankita@in.ibm.com \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masbock@us.ibm.com \
    --cc=oakad@yahoo.com \
    --cc=rubini@vision.unipv.it \
    --cc=sascha@saschahauer.de \
    /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

all inboxes | Powered by JetHome®