From: Dave Hansen <haveblue@us.ibm.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-arch@vger.kernel.org
Subject: Re: [PATCH 3/9] actual generic PAGE_SIZE infrastructure
Date: Tue, 05 Sep 2006 10:52:51 -0700 [thread overview]
Message-ID: <1157478771.3186.30.camel@localhost.localdomain> (raw)
In-Reply-To: <1157434669.2413.30.camel@shinybook.infradead.org>
On Mon, 2006-09-04 at 22:37 -0700, David Woodhouse wrote:
> The above can be summarised: In general, please remember to run
> 'make headers_install' and check the sanity of the result if you're
> making changes which are going to affect user-visible headers.
Did you spot anything that looked like a problem?
How do I check the sanity? Just that none of my headers showed up in
the new include directory. Or, if they did, that all of their meat is
inside of an #ifdef __KERNEL__?
-- Dave
next prev parent reply other threads:[~2006-09-05 17:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-01 19:08 [PATCH 0/9] generic PAGE_SIZE infrastructure (v5) Dave Hansen
2006-09-01 19:08 ` [PATCH 1/9] put alignment macros in align.h Dave Hansen
2006-09-01 19:08 ` [PATCH 2/9] conditionally define generic get_order() (ARCH_HAS_GET_ORDER) Dave Hansen
2006-09-01 19:08 ` [PATCH 4/9] ia64 generic PAGE_SIZE Dave Hansen
2006-09-01 19:08 ` [PATCH 3/9] actual generic PAGE_SIZE infrastructure Dave Hansen
2006-09-05 5:28 ` David Woodhouse
2006-09-05 5:37 ` David Woodhouse
2006-09-05 17:52 ` Dave Hansen [this message]
2006-09-05 18:39 ` David Woodhouse
2006-09-05 5:49 ` Arnd Bergmann
2006-09-05 6:14 ` David Woodhouse
2006-09-01 19:08 ` [PATCH 5/9] sparc64 generic PAGE_SIZE Dave Hansen
2006-09-01 19:08 ` [PATCH 6/9] mips " Dave Hansen
2006-09-01 19:08 ` [PATCH 7/9] parisc " Dave Hansen
2006-09-01 19:08 ` [PATCH 8/9] powerpc " Dave Hansen
2006-09-01 19:08 ` [PATCH 9/9] convert the "easy" architectures to " Dave Hansen
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=1157478771.3186.30.camel@localhost.localdomain \
--to=haveblue@us.ibm.com \
--cc=dwmw2@infradead.org \
--cc=linux-arch@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