From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: The drivers Kconfig structure: oddities and exceptions
Date: Thu, 7 Dec 2006 08:28:24 -0800 [thread overview]
Message-ID: <20061207082824.40c46170.randy.dunlap@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0612070405510.15805@localhost.localdomain>
On Thu, 7 Dec 2006 04:36:25 -0500 (EST) Robert P. J. Day wrote:
>
> as a followup to my previous patch (and before i build on top of
> that), perhaps someone can clarify some of these bits of curiosity:
>
> 1) although "Sound" is listed in the Device Drivers menu, its actual
> source directory is at the top level of the kernel source tree, and
> it's the *only* entry in Device Drivers that requires sourcing from
> the top-level directory. any reason for this? it just kind of stands
> out as a weird exception to the rule.
sound/ (ALSA) was a replacement for the OSS sound drivers and
needed a different directory to live/work in, that's all.
They are still Device Drivers. Don't get hung up on where
the directory is.
(part 2 omitted)
---
~Randy
prev parent reply other threads:[~2006-12-07 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 9:36 Robert P. J. Day
2006-12-07 16:28 ` Randy Dunlap [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=20061207082824.40c46170.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
/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®