All of lore.kernel.org
 help / color / mirror / Atom feed
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 10:01:49 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1001131000350.17529@localhost> (raw)
In-Reply-To: <20100113131539.GA3141@stud.informatik.uni-erlangen.de>

On Wed, 13 Jan 2010, Christoph Egger wrote:

> On Wed, Jan 13, 2010 at 07:05:33AM -0500, Robert P. J. Day wrote:
> >
> >   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
>
> 	Jep I stumbled upon your reports while having a closer look at
> what we found. Strangely while you did find somewhere around 250
> such Issues we are at 90[0] if you count #define-ed CONFIG_* to the
> errors. I'll probably try to look at the difference between our
> results.

  regarding that last point, there's still a lot of explicit
CONFIG_-prefixed macros, which are massively discouraged since all
CONFIG_-prefixed symbols are supposed to be reserved solely for the
Kconfig namespace.

rday
--


========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================

  parent reply	other threads:[~2010-01-13 15:02 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
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 [this message]
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.1001131000350.17529@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 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.