From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Christoph Egger <siccegge@stud.informatik.uni-erlangen.de>
Cc: linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@stericsson.com>,
sameo@linux.intel.com,
Reinhard.Tartler@informatik.uni-erlangen.de
Subject: Re: [PATCH] typo in kernel source (DEBUGFS)
Date: Wed, 13 Jan 2010 07:05:33 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.1001130704190.532@localhost> (raw)
In-Reply-To: <20100113115712.GA7398@faui49.informatik.uni-erlangen.de>
On Wed, 13 Jan 2010, Christoph Egger wrote:
> Hi all!
>
> As part of the VAMOS[0] research project at the University of
> Erlangen we're checking referential integrity between kernel KConfig
> options and in-code Conditional blocks.
>
> While working on this we detected a spelling error in
> drivers/mfd/ab3100-otp.c which can be corrected using the attached
> patch.
>
> Please keep me informed of this patch getting confirmed /
> merged so we can keep track of it.
>
> Regards
>
> Christoph Egger
>
> [0] http://vamos1.informatik.uni-erlangen.de/
just FYI, the same information can be found where i post the output
from my kernel scanning scripts. specifically, that very typo is
already documented here:
http://www.crashcourse.ca/wiki/index.php/Badref_CONFIG_variables#mfd
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next prev parent reply other threads:[~2010-01-13 12:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 11:57 [PATCH] typo in kernel source (DEBUGFS) Christoph Egger
2010-01-13 12:05 ` Robert P. J. Day [this message]
2010-01-13 13:15 ` Christoph Egger
2010-01-13 13:19 ` Robert P. J. Day
2010-01-13 15:01 ` Robert P. J. Day
2010-01-13 12:16 ` Robert P. J. Day
2010-01-14 10:07 ` Linus Walleij
2010-01-15 14:01 ` Jiri Kosina
2010-01-15 16:54 ` Jiri Kosina
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.1001130704190.532@localhost \
--to=rpjday@crashcourse.ca \
--cc=Reinhard.Tartler@informatik.uni-erlangen.de \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=siccegge@stud.informatik.uni-erlangen.de \
/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