From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: what is the value of the macro "__setup_param"?
Date: Fri, 24 Aug 2007 05:32:29 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0708240532160.14757@localhost.localdomain> (raw)
In-Reply-To: <20070824093738.GA30705@stusta.de>
On Fri, 24 Aug 2007, Adrian Bunk wrote:
> On Fri, Aug 24, 2007 at 05:19:29AM -0400, Robert P. J. Day wrote:
> >
> > perhaps i'm missing it, but it seems that the macro __setup_param is
> > entirely superfluous:
> >
> > $ grep -rw __setup_param *
> > include/linux/init.h:#define __setup_param(str, unique_id, fn, early) \
> > include/linux/init.h: __setup_param(str, unique_id, NULL, 0)
> > include/linux/init.h: __setup_param(str, fn, fn, 0)
> > include/linux/init.h: __setup_param(str, fn, fn, 1)
> > include/linux/init.h:#define __setup_param(str, unique_id, fn) /* nothing */
> > $
> >
> > or am i must misreading something badly?
>
> You miss that the inner 3 lines of your grep result are the usages...
i need more sleep.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
next prev parent reply other threads:[~2007-08-24 9:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-24 9:19 Robert P. J. Day
2007-08-24 9:37 ` Adrian Bunk
2007-08-24 9:32 ` Robert P. J. Day [this message]
2007-08-24 9:50 ` Paul Mundt
2007-08-24 9:49 ` Robert P. J. Day
2007-08-24 10:02 ` Paul Mundt
2007-08-24 10:01 ` Robert P. J. Day
2007-08-24 11:29 ` Satyam Sharma
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=Pine.LNX.4.64.0708240532160.14757@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=bunk@kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®