From: Johannes Weiner <jw@emlix.com>
To: Chris Zankel <chris@zankel.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch 1/7] xtensa: kernel/traps.c: include hardirq.h
Date: Wed, 11 Mar 2009 14:36:00 +0100 [thread overview]
Message-ID: <E1LhOad-0000ch-KG@mailer.emlix.com> (raw)
In-Reply-To: <E1LeBSI-0003Yl-Oq@mailer.emlix.com>
On Mon, Mar 02, 2009 at 05:42:58PM +0100, Johannes Weiner wrote:
> The file refers to in_interrupt() so hardirq.h must be included.
>
> Signed-off-by: Johannes Weiner <jw@emlix.com>
> ---
> arch/xtensa/kernel/traps.c | 1 +
> 1 file changed, 1 insertion(+)
>
> --- a/arch/xtensa/kernel/traps.c
> +++ b/arch/xtensa/kernel/traps.c
> @@ -25,6 +25,7 @@
>
> #include <linux/kernel.h>
> #include <linux/sched.h>
> +#include <linux/hardirq.h>
> #include <linux/init.h>
> #include <linux/module.h>
> #include <linux/stringify.h>
This is obsoleted by Alexey's fix in mainline:
5a891ed xtensa: fix compilation somewhat
next prev parent reply other threads:[~2009-03-11 13:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090302164257.477296438@emlix.com>
2009-03-02 16:42 ` Johannes Weiner
2009-03-11 13:36 ` Johannes Weiner [this message]
2009-03-02 16:42 ` [patch 2/7] xtensa: remove redefinition of XCHAL_MMU_ASID_BITS Johannes Weiner
2009-03-02 16:43 ` [patch 3/7] xtensa: beat Kconfig into shape Johannes Weiner
2009-03-02 16:43 ` [patch 4/7] xtensa: use correct stack pointer for stack traces Johannes Weiner
2009-03-02 16:43 ` [patch 5/7] xtensa: fix init_bootmem_node() argument order Johannes Weiner
2009-03-02 16:43 ` [patch 6/7] xtensa: dont make bootmem bitmap larger than required Johannes Weiner
2009-03-02 16:43 ` [patch 7/7] xtensa: cope with ram beginning at higher addresses Johannes Weiner
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=E1LhOad-0000ch-KG@mailer.emlix.com \
--to=jw@emlix.com \
--cc=chris@zankel.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®