From: Andi Kleen <andi@firstfloor.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Andi Kleen <andi@firstfloor.org>,
ebiederm@xmission.com, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] use kexec_kernel.h for the kernel-only stuff [Was: [PATCH] Export kexec.h]
Date: Sat, 19 Jun 2010 21:53:45 +0200 [thread overview]
Message-ID: <20100619195345.GT18946@basil.fritz.box> (raw)
In-Reply-To: <20100619182419.GA22079@merkur.ravnborg.org>
On Sat, Jun 19, 2010 at 08:24:19PM +0200, Sam Ravnborg wrote:
> On Sat, Jun 19, 2010 at 03:22:35PM +0200, Andi Kleen wrote:
> > Export kexec.h
> >
> > kexec_load is a system call and it needs a header
> > file with its input arguments.
> >
> > Export the parts of kexec.h needed for this.
>
> Rather than introducing yet another file where
> only a fraction is exported how about a split
> where we put the kernel specific definitions in kexec_kernel.h.
> And kexec.h is the userspace interface (which is included
> by kexec_kernel.h).
>
> We did it like this for pps some time ago.
Would work for me too, I have no strong opinion either way.
Being naturally lazy, I just went with the simpler patch
myself.
-Andi
next prev parent reply other threads:[~2010-06-19 19:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-19 13:22 [PATCH] Export kexec.h Andi Kleen
2010-06-19 18:24 ` [RFC] use kexec_kernel.h for the kernel-only stuff [Was: [PATCH] Export kexec.h] Sam Ravnborg
2010-06-19 19:53 ` Andi Kleen [this message]
2010-06-20 8:23 ` [PATCH] kexec: export kexec.h to userspace Sam Ravnborg
2010-06-20 8:56 ` Eric W. Biederman
2010-06-20 8:56 ` Eric W. Biederman
2010-06-20 9:23 ` Andi Kleen
2010-06-20 9:23 ` Andi Kleen
2010-07-16 6:54 ` Simon Horman
2010-07-16 6:54 ` Simon Horman
2010-06-19 19:13 ` [PATCH] Export kexec.h Eric W. Biederman
2010-06-19 19:13 ` Eric W. Biederman
2010-06-19 19:44 ` Andi Kleen
2010-06-19 19:44 ` Andi Kleen
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=20100619195345.GT18946@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.