From: Borislav Petkov <bp@amd64.org>
To: Jim Cromie <jim.cromie@gmail.com>
Cc: rusty@rustcorp.com.au, linux-kernel@vger.kernel.org,
pebolle@tiscali.nl, bp@amd64.org, pawel.moll@arm.com,
jbaron@redhat.com, gregkh@linuxfoundation.org
Subject: Re: [PATCH] init: add comments to keep initcall-names in sync with initcall levels
Date: Fri, 15 Jun 2012 12:29:06 +0200 [thread overview]
Message-ID: <20120615102906.GA6083@aftab.osrc.amd.com> (raw)
In-Reply-To: <1339711260-1349-1-git-send-email-jim.cromie@gmail.com>
On Thu, Jun 14, 2012 at 04:00:59PM -0600, Jim Cromie wrote:
> main.c has initcall_level_names[] for parse_args to print in debug messages,
> add comments to keep them in sync with initcalls defined in init.h.
>
> Also add "loadable" into comment re not using *_initcall macros in
> modules, to disambiguate from kernel/params.c and other builtins.
>
> Signed-off-by: Jim Cromie <jim.cromie@gmail.com>
This time I actually build-tested it.
Acked-by: Borislav Petkov <borislav.petkov@amd.com>
Thanks.
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
next prev parent reply other threads:[~2012-06-15 10:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 22:00 [PATCH] init: add comments to keep initcall-names in sync with initcall levels Jim Cromie
2012-06-15 10:29 ` Borislav Petkov [this message]
2012-06-18 6:34 ` Rusty Russell
[not found] <20120612105913.GA8404@aftab.osrc.amd.com>
2012-06-14 18:51 ` Jim Cromie
2012-06-14 19:01 ` Borislav Petkov
2012-06-14 19:23 ` Paul Bolle
2012-06-14 19:47 ` Borislav Petkov
2012-06-14 20:32 ` Jim Cromie
2012-06-14 21:21 ` Paul Bolle
2012-06-14 21:41 ` Borislav Petkov
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=20120615102906.GA6083@aftab.osrc.amd.com \
--to=bp@amd64.org \
--cc=gregkh@linuxfoundation.org \
--cc=jbaron@redhat.com \
--cc=jim.cromie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=pebolle@tiscali.nl \
--cc=rusty@rustcorp.com.au \
/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