[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060718210950.GG2654@sequoia.sous-sol.org>
Date: Tue, 18 Jul 2006 14:09:50 -0700
From: Chris Wright <chrisw@...s-sol.org>
To: David Miller <davem@...emloft.net>
Cc: chrisw@...s-sol.org, linux-kernel@...r.kernel.org,
virtualization@...ts.osdl.org, xen-devel@...ts.xensource.com,
jeremy@...p.org, ak@...e.de, akpm@...l.org, rusty@...tcorp.com.au,
zach@...are.com, ian.pratt@...source.com,
Christian.Limpach@...cam.ac.uk, netdev@...r.kernel.org
Subject: Re: [RFC PATCH 32/33] Add the Xen virtual network device driver.
* David Miller (davem@...emloft.net) wrote:
> From: Chris Wright <chrisw@...s-sol.org>
> Date: Tue, 18 Jul 2006 00:00:32 -0700
>
> > +#ifdef CONFIG_XEN_BALLOON
> > +#include <xen/balloon.h>
> > +#endif
>
> Let's put the ifdefs in xen/balloon.h not in the files
> including it.
>
> > +#ifdef CONFIG_XEN_BALLOON
> > + /* Tell the ballon driver what is going on. */
> > + balloon_update_driver_allowance(i);
> > +#endif
>
> Similarly let's define empty do-nothing functions in
> xen/balloon.h when the config option isn't set so we
> don't need to crap up the C sources with these ifdefs.
Yeah, sorry it's kept more as a reminder to me. Upstream Xen doesn't do
this, but this patchset doesn't support ballooning yet, so there just is
not xen/balloon.h in the set. When merging with upstream Xen there's
patch rejects either way, so I agree, better to just drop this since
it's just future placeholder.
thanks,
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists