From: David Daney <ddaney.cavm@gmail.com>
To: Jim Quinlan <jim2101024@gmail.com>, ralf@linux-mips.org
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH V2 1/2] asm-offsets.c: adding #define to break circular dependency
Date: Wed, 29 Aug 2012 16:01:58 -0700 [thread overview]
Message-ID: <503E9F66.9030200@gmail.com> (raw)
In-Reply-To: <1346279647-27955-1-git-send-email-jim2101024@gmail.com>
On 08/29/2012 03:34 PM, Jim Quinlan wrote:
> irqflags.h depends on asm-offsets.h, but asm-offsets.h depends
> on irqflags.h when generating asm-offsets.h.
What is there in irqflags.h that is required by asm-offsets.c?
Why can't the include tangle be undone so that that part can be factored
out to a separate file?
> Adding a definition
> to the top of asm-offsets.c allows us to break this circle. There
> is a similar define in bounds.c
>
> Signed-off-by: Jim Quinlan <jim2101024@gmail.com>
> ---
> arch/mips/kernel/asm-offsets.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/arch/mips/kernel/asm-offsets.c b/arch/mips/kernel/asm-offsets.c
> index 6b30fb2..035f167 100644
> --- a/arch/mips/kernel/asm-offsets.c
> +++ b/arch/mips/kernel/asm-offsets.c
> @@ -8,6 +8,7 @@
> * Kevin Kissell, kevink@mips.com and Carsten Langgaard, carstenl@mips.com
> * Copyright (C) 2000 MIPS Technologies, Inc.
> */
> +#define __GENERATING_OFFSETS_S
> #include <linux/compat.h>
> #include <linux/types.h>
> #include <linux/sched.h>
>
next prev parent reply other threads:[~2012-08-29 23:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 22:34 [PATCH V2 1/2] asm-offsets.c: adding #define to break circular dependency Jim Quinlan
2012-08-29 22:34 ` [PATCH V2 2/2] MIPS: irqflags.h: make funcs preempt-safe for non-mipsr2 Jim Quinlan
2012-08-30 16:41 ` David Daney
2012-08-29 23:01 ` David Daney [this message]
2012-08-30 14:06 ` [PATCH V2 1/2] asm-offsets.c: adding #define to break circular dependency Jim Quinlan
2012-08-30 14:15 ` Ralf Baechle
2012-08-30 20:35 ` Jim Quinlan
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=503E9F66.9030200@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=jim2101024@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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