From: Amerigo Wang <xiyou.wangcong@gmail.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: trivial@kernel.org, linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net,
Jeff Dike <jdike@addtoit.com>
Subject: Re: [PATCH 3/5] uml: Fix warning due to missing task_struct declaration
Date: Tue, 20 Apr 2010 18:09:49 +0800 [thread overview]
Message-ID: <20100420100949.GB5317@cr0.nay.redhat.com> (raw)
In-Reply-To: <1d97cd7761a1eae73923b1adda4c6915a0647bb3.1271713955.git.jan.kiszka@web.de>
On Mon, Apr 19, 2010 at 11:53:06PM +0200, Jan Kiszka wrote:
>We can't pull in linux/sched.h, so just declare the struct.
>
Did you meet any build error? If yes, please include it.
Thanks.
>Signed-off-by: Jan Kiszka <jan.kiszka@web.de>
>---
> arch/um/sys-i386/asm/elf.h | 2 ++
> arch/um/sys-x86_64/asm/elf.h | 2 ++
> 2 files changed, 4 insertions(+), 0 deletions(-)
>
>diff --git a/arch/um/sys-i386/asm/elf.h b/arch/um/sys-i386/asm/elf.h
>index e64cd41..a979a22 100644
>--- a/arch/um/sys-i386/asm/elf.h
>+++ b/arch/um/sys-i386/asm/elf.h
>@@ -75,6 +75,8 @@ typedef struct user_i387_struct elf_fpregset_t;
> pr_reg[16] = PT_REGS_SS(regs); \
> } while (0);
>
>+struct task_struct;
>+
> extern int elf_core_copy_fpregs(struct task_struct *t, elf_fpregset_t *fpu);
>
> #define ELF_CORE_COPY_FPREGS(t, fpu) elf_core_copy_fpregs(t, fpu)
>diff --git a/arch/um/sys-x86_64/asm/elf.h b/arch/um/sys-x86_64/asm/elf.h
>index 49655c8..d760967 100644
>--- a/arch/um/sys-x86_64/asm/elf.h
>+++ b/arch/um/sys-x86_64/asm/elf.h
>@@ -95,6 +95,8 @@ typedef struct user_i387_struct elf_fpregset_t;
> (pr_reg)[25] = 0; \
> (pr_reg)[26] = 0;
>
>+struct task_struct;
>+
> extern int elf_core_copy_fpregs(struct task_struct *t, elf_fpregset_t *fpu);
>
> #define ELF_CORE_COPY_FPREGS(t, fpu) elf_core_copy_fpregs(t, fpu)
>--
>1.6.0.2
>
>--
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2010-04-20 10:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 21:53 [PATCH 0/5] uml: Some trivial cleanups Jan Kiszka
2010-04-19 21:53 ` [PATCH 1/5] uml: Remove unused variable from line driver Jan Kiszka
2010-04-20 8:32 ` Amerigo Wang
2010-04-20 14:31 ` Jiri Kosina
2010-04-19 21:53 ` [PATCH 2/5] uml: Drop private round_down definition Jan Kiszka
2010-04-20 8:33 ` Amerigo Wang
2010-04-20 14:25 ` Jeff Dike
2010-04-20 15:49 ` Jiri Kosina
2010-04-20 14:35 ` Jiri Kosina
2010-04-20 16:52 ` [uml-devel] " Jeff Dike
2010-04-20 17:18 ` Jiri Kosina
2010-04-19 21:53 ` [PATCH 3/5] uml: Fix warning due to missing task_struct declaration Jan Kiszka
2010-04-20 10:09 ` Amerigo Wang [this message]
2010-04-20 14:30 ` Jeff Dike
2010-04-20 17:09 ` Jan Kiszka
2010-04-20 23:43 ` Jiri Kosina
2010-04-21 6:06 ` Amerigo Wang
2010-04-21 9:38 ` Jiri Kosina
2010-04-21 10:43 ` Amerigo Wang
2010-04-21 10:49 ` Jiri Kosina
2010-04-19 21:53 ` [PATCH 4/5] uml: i386: Avoid redefinition of NR_syscalls Jan Kiszka
2010-04-20 10:10 ` Amerigo Wang
2010-04-20 17:14 ` Jan Kiszka
2010-04-21 6:12 ` Amerigo Wang
2010-05-10 21:38 ` Jiri Kosina
2010-04-19 21:53 ` [PATCH 5/5] uml: Clean up asm/system.h Jan Kiszka
2010-04-20 10:14 ` Amerigo Wang
2010-04-20 14:33 ` Jiri Kosina
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=20100420100949.GB5317@cr0.nay.redhat.com \
--to=xiyou.wangcong@gmail.com \
--cc=jan.kiszka@web.de \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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
Powered by JetHome