From: rpjday@crashcourse.ca (Robert P. J. Day)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP: Remove unused CONFIG MACH_OMAP_HTCWIZARD
Date: Sat, 26 Sep 2009 21:51:22 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0909262148100.6153@localhost> (raw)
In-Reply-To: <3d374d00909261836g38ceceb0p3fed39ac62103c33@mail.gmail.com>
On Sun, 27 Sep 2009, Alistair Buxton wrote:
> 2009/9/26 Jaswinder Singh Rajput <jaswinder@kernel.org>:
> >
> > Remove unused CONFIG MACH_OMAP_HTCWIZARD from Kconfig
>
> Don't do it please! We're working on it.... board file is coming
> very soon.
i've noticed that happening fairly often -- feature infrastructure
is added before the feature itself. at the risk of sounding all
preachy and everything, that sort of thing should be avoided in order
to keep the history cleaner. and because that's *exactly* the sort of
thing that, occasionally, produces the kind of historical cruft that
leaves unused CONFIG variables lying around when a feature is
abandoned in midstream.
ok, i'll stop preaching now.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next prev parent reply other threads:[~2009-09-27 1:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-26 14:11 [PATCH] ARM: OMAP: Remove unused CONFIG MACH_OMAP_HTCWIZARD Jaswinder Singh Rajput
2009-09-27 1:36 ` Alistair Buxton
2009-09-27 1:51 ` Robert P. J. Day [this message]
2009-09-27 1:48 ` Zebediah C. McClure
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=alpine.LFD.2.00.0909262148100.6153@localhost \
--to=rpjday@crashcourse.ca \
--cc=linux-arm-kernel@lists.infradead.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).