From: Gawain Lynch <gawain.lynch@bigpond.com>
To: xen-devel@lists.xensource.com, "Mike D. Day" <ncmike@us.ibm.com>
Subject: Re: [PATCH] [RFC] sysfs support for xen linux
Date: Wed, 11 Jan 2006 02:23:20 +1300 [thread overview]
Message-ID: <1136899400.25819.17.camel@legolas.felicity.net.au> (raw)
In-Reply-To: <43C2F324.4020407@us.ibm.com>
> diff -r c08884b412da -r cec2fc0a07c6 linux-2.6-xen-sparse/arch/xen/kernel/xen_sysfs.c
> --- /dev/null Mon Jan 9 21:55:13 2006
> +++ b/linux-2.6-xen-sparse/arch/xen/kernel/xen_sysfs.c Mon Jan 9 23:07:04 2006
<SNIP>
> +#ifndef BOOL
> +#define BOOL int
> +#endif
> +
> +#ifndef FALSE
> +#define FALSE 0
> +#endif
> +
> +#ifndef TRUE
> +#define TRUE 1
> +#endif
> +
> +#ifndef NULL
> +#define NULL 0
> +#endif
These are already defined in kernel and a favourite nit pick on LKML.
> +struct xen_sysfs_attr
> +{
struct xen_sysfs_attr {
New line for braces are reserved for functions()
> +struct xen_sysfs_object
> +{
struct xen_sysfs_object {
> --- /dev/null Mon Jan 9 21:55:13 2006
> +++ b/linux-2.6-xen-sparse/include/asm-xen/xen_sysfs.h Mon Jan 9 23:07:04 2006
<SNIP>
> +#ifndef BOOL
> +#define BOOL int
> +#endif
> +
> +#ifndef FALSE
> +#define FALSE 0
> +#endif
> +
> +#ifndef TRUE
> +#define TRUE 1
> +#endif
> +
> +#ifndef NULL
> +#define NULL 0
> +#endif
>
See above...
next prev parent reply other threads:[~2006-01-10 13:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 23:35 [PATCH] [RFC] sysfs support for xen linux Mike D. Day
2006-01-10 1:09 ` Christopher G. Stach II
2006-01-10 10:13 ` Keir Fraser
2006-01-10 13:23 ` Gawain Lynch [this message]
2006-01-12 1:44 ` Chris Wright
-- strict thread matches above, loose matches on Subject: below --
2006-01-10 12:58 Mike D. Day
2006-01-11 10:21 ` Keir Fraser
2006-01-11 16:12 Mike D. Day
2006-01-11 16:05 ` Mark Williamson
2006-01-11 16:35 ` Keir Fraser
2006-01-11 16:40 ` Ronald G Minnich
2006-01-11 16:28 Mike D. Day
2006-01-11 16:28 ` Mark Williamson
2006-01-11 16:50 ` Anthony Liguori
2006-01-11 17:03 ` Daniel Stekloff
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=1136899400.25819.17.camel@legolas.felicity.net.au \
--to=gawain.lynch@bigpond.com \
--cc=ncmike@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/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.