From: Jes Sorensen <jes@sgi.com>
To: Glauber de Oliveira Costa <glommer@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Rusty Russell <rusty@rustcorp.com.au>, lguest <lguest@ozlabs.org>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
virtualization <virtualization@lists.linux-foundation.org>,
Carsten Otte <cotte@de.ibm.com>
Subject: Re: [PATCH 2/7] Added generic lg.h in lguest directory.
Date: Thu, 09 Aug 2007 14:06:15 +0200 [thread overview]
Message-ID: <46BB0337.6040701@sgi.com> (raw)
In-Reply-To: <5d6222a80708081756r21bbc7e3ifd357c9c548ac57f@mail.gmail.com>
Glauber de Oliveira Costa wrote:
> On 8/8/07, Steven Rostedt <rostedt@goodmis.org> wrote:
>> Add a generic lg.h file to call the architecture specific one.
>>
>> diff --git a/drivers/lguest/lg.h b/drivers/lguest/lg.h
>> new file mode 100644
>> index 0000000..4c4356e
>> --- /dev/null
>> +++ b/drivers/lguest/lg.h
>> @@ -0,0 +1,3 @@
>> +#ifdef CONFIG_X86_32
>> +#include "i386/lg.h"
>> +#endif
>
> Wouldn't it be cleaner to do something like the asm/ includes?
> I understand that lguest now lives in drivers/ and so we don't put
> headers directly in asm-i386 , but we could come up with a similar
> thing here.
Yeah, that would be much better, and I don't like having something in
a header file including arch specific files like that. I target to get
lguest going on non x86, so I would like to encourage anyone to think
more than x86 when trying to seperate out something :)
IMHO we should avoid any header files with asm specific code in
drivers/lguest - in a way I prefer having arch/<foo>/lguest to
drivers/lguest/<arch>, would be more esthetically compliant with
the include/asm-<arch> approach too, but thats not a big deal.
Cheers,
Jes
next prev parent reply other threads:[~2007-08-09 12:07 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 0:32 [PATCH 0/7] Modify lguest32 to make room for lguest64 Steven Rostedt
2007-08-09 0:32 ` [PATCH 1/7] Move lg.h to the i386 specific lguest directory Steven Rostedt
2007-08-09 0:32 ` Steven Rostedt
2007-08-09 0:32 ` [PATCH 2/7] Added generic lg.h in " Steven Rostedt
2007-08-09 0:56 ` Glauber de Oliveira Costa
2007-08-09 0:56 ` Glauber de Oliveira Costa
2007-08-09 12:06 ` Jes Sorensen [this message]
2007-08-09 12:06 ` Jes Sorensen
2007-08-09 1:45 ` Stephen Rothwell
2007-08-09 1:45 ` Stephen Rothwell
2007-08-09 2:17 ` Steven Rostedt
2007-08-09 2:17 ` Steven Rostedt
2007-08-09 0:32 ` Steven Rostedt
2007-08-09 0:32 ` [PATCH 3/7] Move the lguest files that are i386 specific Steven Rostedt
2007-08-09 0:32 ` Steven Rostedt
2007-08-09 0:32 ` [PATCH 4/7] Moved the io struct up to the generic lg.h Steven Rostedt
2007-08-09 1:51 ` Stephen Rothwell
2007-08-09 2:19 ` Steven Rostedt
2007-08-09 2:19 ` Steven Rostedt
2007-08-09 12:26 ` Jes Sorensen
2007-08-09 12:26 ` Jes Sorensen
2007-08-09 12:40 ` Steven Rostedt
2007-08-09 12:40 ` Steven Rostedt
2007-08-09 1:51 ` Stephen Rothwell
2007-08-09 0:32 ` Steven Rostedt
2007-08-09 0:32 ` [PATCH 5/7] Change lguest launcher to use asm generic include Steven Rostedt
2007-08-09 1:05 ` Glauber de Oliveira Costa
2007-08-09 1:05 ` Glauber de Oliveira Costa
2007-08-11 3:11 ` Rusty Russell
2007-08-11 3:11 ` Rusty Russell
2007-08-09 0:32 ` Steven Rostedt
2007-08-09 0:32 ` [PATCH 6/7] Remove __pa() use in hvc_lguest Steven Rostedt
2007-08-09 0:32 ` Steven Rostedt
2007-08-09 0:32 ` [PATCH 7/7] Move lguest_dma_info into generic lg.h Steven Rostedt
2007-08-09 0:32 ` Steven Rostedt
2007-08-11 3:42 ` [PATCH 0/7] Modify lguest32 to make room for lguest64 Rusty Russell
2007-08-13 9:50 ` Jes Sorensen
2007-08-13 9:50 ` Jes Sorensen
2007-08-13 15:01 ` Jes Sorensen
2007-08-11 3:42 ` Rusty Russell
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=46BB0337.6040701@sgi.com \
--to=jes@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=cotte@de.ibm.com \
--cc=glommer@gmail.com \
--cc=lguest@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.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.