From: Sam Ravnborg <sam@ravnborg.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: David Howells <dhowells@redhat.com>,
torvalds@osdl.org, akpm@osdl.org, bernds_cb1@t-online.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] FRV: Introduce asm-offsets for FRV arch
Date: Wed, 5 Jul 2006 18:48:28 +0200 [thread overview]
Message-ID: <20060705164828.GA8196@mars.ravnborg.org> (raw)
In-Reply-To: <1152117585.2987.21.camel@pmac.infradead.org>
> > It is no loner needed to include <linux/config.h>.
>
> Then let's kill it entirely... well, I've left it with a #error for now
> because otherwise people will just keep asking where it is.
That will be bad for all out-of-tree stuff.
Now they have to track down if the kernel they build for
are before or after we stuffed in #error in config.h
A #warning would be more appropriate.
Sam
next prev parent reply other threads:[~2006-07-05 16:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 13:24 [PATCH 1/5] FDPIC: Fix FDPIC compile errors David Howells
2006-07-05 13:24 ` [PATCH 2/5] FRV: Fix FRV arch " David Howells
2006-07-05 13:24 ` [PATCH 3/5] NOMMU: Fix execution off of ramfs with mmap() David Howells
2006-07-05 13:24 ` [PATCH 4/5] [PATCH] FDPIC: Add coredump capability for the ELF-FDPIC binfmt David Howells
2006-07-05 13:24 ` [PATCH 5/5] FRV: Introduce asm-offsets for FRV arch David Howells
2006-07-05 14:41 ` Sam Ravnborg
2006-07-05 16:39 ` David Woodhouse
2006-07-05 16:48 ` Sam Ravnborg [this message]
2006-07-05 16:50 ` David Woodhouse
2006-07-05 16:58 ` Sam Ravnborg
2006-07-05 17:10 ` David Woodhouse
2006-07-05 17:29 ` David Woodhouse
2006-07-05 17:03 ` Linus Torvalds
2006-07-05 17:18 ` David Woodhouse
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=20060705164828.GA8196@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@osdl.org \
--cc=bernds_cb1@t-online.de \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®