From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: Jaroslav Kysela <perex@suse.cz>
Cc: <linux-kernel@vger.kernel.org>, <linux-sound@vger.kernel.org>
Subject: [TRIVIAL][2.6.0-test2] move "config SOUND" to sound/Kconfig
Date: Fri, 1 Aug 2003 02:48:32 +0200 (MET DST) [thread overview]
Message-ID: <Pine.SOL.4.30.0308010240010.3421-100000@mion.elka.pw.edu.pl> (raw)
Hi,
http://home.elka.pw.edu.pl/~bzolnier/sound-Kconfig.patch
[ I think there is no need to increase traffic... ]
move "config SOUND" to sound/Kconfig
Allows all architectures to simply include the sound/Kconfig file.
Now somebody can finally update comment for CONFIG_SOUND ;-).
arch/alpha/Kconfig | 34 ----------------------------------
arch/arm/Kconfig | 35 ++---------------------------------
arch/arm26/Kconfig | 35 ++---------------------------------
arch/cris/Kconfig | 35 -----------------------------------
arch/i386/Kconfig | 34 ----------------------------------
arch/ia64/Kconfig | 19 -------------------
arch/m68k/Kconfig | 10 +---------
arch/m68knommu/Kconfig | 34 ----------------------------------
arch/parisc/Kconfig | 34 ----------------------------------
arch/ppc/Kconfig | 37 -------------------------------------
arch/ppc64/Kconfig | 34 ----------------------------------
arch/sh/Kconfig | 34 ----------------------------------
arch/sparc/Kconfig | 35 -----------------------------------
arch/sparc64/Kconfig | 35 -----------------------------------
arch/v850/Kconfig | 34 ----------------------------------
arch/x86_64/Kconfig | 35 -----------------------------------
sound/Kconfig | 41 +++++++++++++++++++++++++++++++++++++++++
17 files changed, 46 insertions(+), 509 deletions(-)
--
Bartlomiej
reply other threads:[~2003-08-01 0:49 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=Pine.SOL.4.30.0308010240010.3421-100000@mion.elka.pw.edu.pl \
--to=b.zolnierkiewicz@elka.pw.edu.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@suse.cz \
/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).