From: josh@joshtriplett.org
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Iulia Manda <iulia.manda21@gmail.com>,
tim.bird@sonymobile.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] init: Set initcall_debug to a default value
Date: Tue, 19 May 2015 17:54:52 -0700 [thread overview]
Message-ID: <20150520005452.GC32153@cloud> (raw)
In-Reply-To: <1432028814.9091.68.camel@x220>
On Tue, May 19, 2015 at 11:46:54AM +0200, Paul Bolle wrote:
> On Mon, 2015-05-18 at 14:50 +0300, Iulia Manda wrote:
> > ---
> > include/linux/init.h | 3 ++-
> > init/main.c | 3 +--
> > 2 files changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/include/linux/init.h b/include/linux/init.h
> > index 21b6d76..7c7ee80 100644
> > --- a/include/linux/init.h
> > +++ b/include/linux/init.h
>
> > -extern bool initcall_debug;
> > +DECLARE_CORE_PARAM(initcall_debug, false, bool);
>
> CONFIG_CMDLINE_PARSE will never be set outside of x86, right? So does
> this change nothing for those other architectures?
See comment on the previous patch; this is not x86-specific, and it
should be a config option for all architectures.
- Josh Triplett
next prev parent reply other threads:[~2015-05-20 0:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 11:50 [PATCH 1/3] kernel: Add a new config option to remove command line parsing Iulia Manda
2015-05-18 11:50 ` [PATCH 2/3] linux: Add macros that define and declare a core_param variable Iulia Manda
2015-05-18 11:50 ` [PATCH 3/3] init: Set initcall_debug to a default value Iulia Manda
2015-05-19 9:46 ` Paul Bolle
2015-05-20 0:54 ` josh [this message]
2015-05-19 9:35 ` [PATCH 1/3] kernel: Add a new config option to remove command line parsing Paul Bolle
2015-05-20 0:54 ` josh
2015-05-20 6:29 ` Rob Landley
2015-05-20 15:15 ` [PATCH v2] " Iulia Manda
-- strict thread matches above, loose matches on Subject: below --
2015-04-01 14:34 [PATCH 1/3] " Iulia Manda
2015-04-01 14:34 ` [PATCH 3/3] init: Set initcall_debug to a default value Iulia Manda
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=20150520005452.GC32153@cloud \
--to=josh@joshtriplett.org \
--cc=iulia.manda21@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=tim.bird@sonymobile.com \
/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.