From: Matthew Wilcox <willy@debian.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [Kernel-janitors] Kconfig cleanups
Date: Thu, 15 Jan 2004 04:24:32 +0000 [thread overview]
Message-ID: <20040115042432.GA9684@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20040114065742.GG10711@parcelfarce.linux.theplanet.co.uk>
On Thu, Jan 15, 2004 at 12:20:44AM +0000, Dave Jones wrote:
> Sparc64 has a DRM module for Creator3D, which I *think* is SBUS.
> Yes, Sparc* has to be different and put its DRM Kconfig stuff
> in arch/sparc64/Kconfig instead.
Part of the reason for this cleanup is to remove crap like that from
the arch Kconfig files; keeping all this up to date is one of the least
interesting bits of being an arch maintainer. I'll incorporate removing
this from Sparc64 into my patchset. Thanks.
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2004-01-15 4:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 6:57 [Kernel-janitors] Kconfig cleanups Matthew Wilcox
2004-01-14 19:46 ` Greg KH
2004-01-14 21:05 ` Adrian Bunk
2004-01-14 22:48 ` Matthew Wilcox
2004-01-15 0:20 ` Dave Jones
2004-01-15 4:24 ` Matthew Wilcox [this message]
2004-01-15 11:41 ` Adrian Bunk
2004-01-23 0:36 ` Bjorn Helgaas
2004-01-23 0:36 ` Bjorn Helgaas
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=20040115042432.GA9684@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.