From: Andrew Morton <akpm@linux-foundation.org>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com,
rgetz@blackfin.uclinux.org
Subject: Re: [PATCH 1/4] asm/sections: add text/data checking functions for arches to override
Date: Tue, 23 Jun 2009 19:04:26 -0700 [thread overview]
Message-ID: <20090623190426.d4cc9853.akpm@linux-foundation.org> (raw)
In-Reply-To: <8bd0f97a0906231848u61d07a3j803f51cb26b72dab@mail.gmail.com>
On Tue, 23 Jun 2009 21:48:03 -0400 Mike Frysinger <vapier.adi@gmail.com> wrote:
> > I suppose that for completeness and consistency etc really we should have
> >
> > #define arch_is_kernel_text arch_is_kernel_text
> > #define arch_is_kernel_data arch_is_kernel_data
> >
> > in here.
>
> *shrug* other places that use this style dont include these defines
> for completeness
Examples?
All the ones I can find do things like
#ifndef vmcore_elf_check_arch_cross
#define vmcore_elf_check_arch_cross(x) 0
#endif
> as the define muck is for the header to know about
> (arches providing their own version), not any source code -- they
> shouldnt know anything about the ifdef stuff.
Failing to do the #define will have various tricky failure modes. But
it's more a question of "what is the _right_ thing to do", then doing
that consistently.
> i dont care much either way.
Someone has to.
prev parent reply other threads:[~2009-06-24 2:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 16:22 [PATCH 1/4] asm/sections: add text/data checking functions for arches to override Mike Frysinger
2009-06-17 16:22 ` [PATCH 2/4] kallsyms: use new arch_is_kernel_text() Mike Frysinger
2009-06-17 16:22 ` [PATCH 3/4] lockdep: use new arch_is_kernel_data() Mike Frysinger
2009-06-17 16:22 ` [PATCH 4/4] Blackfin: override text/data checking functions Mike Frysinger
2009-06-23 22:40 ` [PATCH 1/4] asm/sections: add text/data checking functions for arches to override Andrew Morton
2009-06-24 1:48 ` Mike Frysinger
2009-06-24 2:04 ` 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=20090623190426.d4cc9853.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rgetz@blackfin.uclinux.org \
--cc=vapier.adi@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox