From: Tilman Schmidt <tilman@imap.cc>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: "Nigel Cunningham" <ncunningham@crca.org.au>,
"André Goddard Rosa" <andre.goddard@gmail.com>,
trivial@kernel.org, "linux list" <linux-kernel@vger.kernel.org>
Subject: Kernel cleanup Wiki (was: [PATCH 03/16] trivial: fix assorted "through" typos)
Date: Mon, 02 Nov 2009 11:09:21 +0100 [thread overview]
Message-ID: <4AEEAFD1.5070703@imap.cc> (raw)
In-Reply-To: <20091101095208.10d57e8f.rdunlap@xenotime.net>
[-- Attachment #1: Type: text/plain, Size: 1889 bytes --]
Am 01.11.2009 18:52 schrieb Randy Dunlap:
> On Sat, 31 Oct 2009 13:11:29 +0100 Tilman Schmidt wrote:
>
>> Am 31.10.2009 11:17 schrieb Nigel Cunningham:
>>> I've only looked at this one, but something caught my eye...
>>>
>>> André Goddard Rosa wrote:
>>>> diff --git a/arch/blackfin/kernel/cplb-mpu/cplbinit.c
>>>> b/arch/blackfin/kernel/cplb-mpu/cplbinit.c
>>>> index f7b9cdc..b52c1f8 100644
>>>> --- a/arch/blackfin/kernel/cplb-mpu/cplbinit.c
>>>> +++ b/arch/blackfin/kernel/cplb-mpu/cplbinit.c
>>>> @@ -38,7 +38,7 @@ void __init generate_cplb_tables_cpu(unsigned int cpu)
>>>>
>>>> #ifdef CONFIG_BFIN_EXTMEM_DCACHEABLE
>>>> d_cache = CPLB_L1_CHBL;
>>>> -#ifdef CONFIG_BFIN_EXTMEM_WRITETROUGH
>>>> +#ifdef CONFIG_BFIN_EXTMEM_WRITETHROUGH
>>>> d_cache |= CPLB_L1_AOW | CPLB_WT;
>>>> #endif
>>>> #endif
>>> "Surely that can't be the only time?", I thought. But it is - all of the
>>> other #ifdefs are spelled correctly, so you're probably fixing a
>>> hard-to-find bug here! Good catch!
>>>
>>> Makes me wonder if anyone's written a tool to find things like this -
>>> #ifdefs that will never be defined...
>> I seem to remember someone (Joe Perches?) did, and regularly posted
>> results to LKML in the past, but at some point switched to publishing
>> them on a web page instead.
>
> It was Robert PJ Day.
Indeed it was, and kudos to him for doing it.
Please forgive my middle-aged brain for the misattribution.
> See http://www.crashcourse.ca/wiki/index.php/Kernel_cleanup
And sure enough, CONFIG_BFIN_EXTMEM_WRITETROUGH is listed there on the
"Badref CONFIG variables" page.
It seems that page would merit a bit of advertising. :-)
--
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]
next prev parent reply other threads:[~2009-11-02 10:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-31 9:40 [PATCH 03/16] trivial: fix assorted "through" typos André Goddard Rosa
2009-10-31 10:17 ` Nigel Cunningham
2009-10-31 10:22 ` André Goddard Rosa
2009-10-31 12:11 ` Tilman Schmidt
2009-11-01 17:52 ` Randy Dunlap
2009-11-01 21:13 ` Thiago Farina
2009-11-02 10:40 ` ARRAY_SIZE (was: [PATCH 03/16] trivial: fix assorted "through" typos) Tilman Schmidt
2009-11-02 10:09 ` Tilman Schmidt [this message]
2009-11-02 9:18 ` [PATCH 03/16] trivial: fix assorted "through" typos Ingo Molnar
2009-11-02 16:00 ` Jiri Kosina
2009-11-02 16:16 ` André Goddard Rosa
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=4AEEAFD1.5070703@imap.cc \
--to=tilman@imap.cc \
--cc=andre.goddard@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@crca.org.au \
--cc=rdunlap@xenotime.net \
--cc=trivial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox