From: Andrew Morton <akpm@linux-foundation.org>
To: Nathan Lynch <ntl@pobox.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Helge, Seetharaman <sekharan@us.ibm.com>,
Deller <deller@parisc-linux.org>,
linuxppc-dev@ozlabs.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"andi@firstfloor.org" <andi@firstfloor.org>,
Chandra,
"kosaki.motohiro@jp.fujitsu.com" <kosaki.motohiro@jp.fujitsu.com>,
"mpm@selenic.com" <mpm@selenic.com>,
Olof Johansson <olof@lixom.net>,
Wu Fengguang <fengguang.wu@intel.com>,
"adobriyan@gmail.com" <adobriyan@gmail.com>
Subject: Re: [PATCH 5/5] proc: export more page flags in /proc/kpageflags
Date: Tue, 28 Apr 2009 21:50:50 -0700 [thread overview]
Message-ID: <20090428215050.67b7b4db.akpm@linux-foundation.org> (raw)
In-Reply-To: <m38wlkxe9b.fsf@pobox.com>
On Tue, 28 Apr 2009 23:41:52 -0500 Nathan Lynch <ntl@pobox.com> wrote:
> > CONFIG_DEBUG_KERNEL being enabled in distro kernels effectively means
> >
> > #ifdef CONFIG_DEBUG_KERNEL == #if 1
> >
> > as the following patch demos. Now it becomes obviously silly.
>
> Sure, #if 1 is usually silly. But if the point is that DEBUG_KERNEL is
> not supposed to directly affect code generation, then I see two options
> for powerpc:
>
> - remove the #ifdef CONFIG_DEBUG_KERNEL guards from
> arch/powerpc/kernel/sysfs.c, unconditionally enabling the hid/ima
> sysfs attributes, or
>
> - define a new config symbol which governs whether those attributes are
> enabled, and make it depend on DEBUG_KERNEL
yup.
prev parent reply other threads:[~2009-04-29 4:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090428010907.912554629@intel.com>
[not found] ` <20090428014920.769723618@intel.com>
[not found] ` <20090428143244.4e424d36.akpm@linux-foundation.org>
[not found] ` <20090429023842.GA10266@localhost>
2009-04-29 4:41 ` [PATCH 5/5] proc: export more page flags in /proc/kpageflags Nathan Lynch
2009-04-29 4:50 ` Andrew Morton [this message]
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=20090428215050.67b7b4db.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=andi@firstfloor.org \
--cc=deller@parisc-linux.org \
--cc=fengguang.wu@intel.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpm@selenic.com \
--cc=ntl@pobox.com \
--cc=olof@lixom.net \
--cc=sekharan@us.ibm.com \
--cc=sfr@canb.auug.org.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;
as well as URLs for NNTP newsgroup(s).