All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Egger <Christoph.Egger@amd.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [PATCH 2/6] libxl: portiblity fixes
Date: Wed, 28 Jul 2010 11:06:01 +0200	[thread overview]
Message-ID: <201007281106.01632.Christoph.Egger@amd.com> (raw)
In-Reply-To: <19535.2701.407454.1714@mariner.uk.xensource.com>

On Tuesday 27 July 2010 18:34:21 Ian Jackson wrote:
> Christoph Egger writes ("[Xen-devel] [PATCH 2/6] libxl: portiblity fixes"):
> > --- a/tools/libxl/libxl_osdeps.h	Tue Jul 27 13:48:38 2010 +0200
> > +++ b/tools/libxl/libxl_osdeps.h	Tue Jul 27 13:53:12 2010 +0200
> > @@ -23,6 +23,8 @@
> >
> >  #define _GNU_SOURCE
> >
> > +#include <libxl_internal.h>
> > +
>
> This is wrong.  libxl_osdeps.h should not include libxl_internal.h.
>
> > +/* libxl_blktap_enabled:
> > + *    return true if blktap/blktap2 support is available.
> > + */
> > +int libxl_blktap_enabled(struct libxl_ctx *ctx);
>
> This is not what libxl_osdeps.h is for.  These kind of functions can
> be declared in a new section in libxl_internal.h.
>
> Also, you should divide your patches conceptually, rather than
> according to which files they touch.
>
> This patch is wrong because it introduces a couple of function
> declarations but it does not introduce the definitions; your later
> patch which introduces the definitions is wrong because it introduces
> some functions which are intended to replace existing code, but the
> patch does not replace the existing code and the new functions are not
> called anywhere in that patch.

The function declarations are the API and the function defintions
are the OS dependent implementations of the API.
Implementations and use of the API is used in different patches.
This is my understanding of defining and implementing an API
in C.
blktap support for linux and netbsd are very different in their 
implementation.
In netbsd, blktap will be implemented using puffs
(http://netbsd.gw.com/cgi-bin/man-cgi?puffs+3+NetBSD-current)

Christoph

-- 
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

  reply	other threads:[~2010-07-28  9:06 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20 16:31 [PATCH] libxl: blktap2 portiblity fixes Christoph Egger
2010-07-20 16:46 ` Stefano Stabellini
2010-07-21  8:32   ` Christoph Egger
2010-07-23 12:30     ` Stefano Stabellini
2010-07-23 18:05     ` Ian Jackson
2010-07-26 10:56       ` Christoph Egger
2010-07-26 14:53         ` Ian Jackson
2010-07-26 15:00           ` Ian Campbell
2010-07-26 15:12             ` Ian Jackson
2010-07-26 16:01               ` Christoph Egger
2010-07-26 16:05           ` Christoph Egger
2010-07-26 16:36             ` Ian Jackson
2010-07-27 12:07               ` Christoph Egger
2010-07-27 12:15               ` [PATCH 1/6] libxl: " Christoph Egger
2010-07-27 12:16                 ` [PATCH 2/6] " Christoph Egger
2010-07-27 12:17                   ` [PATCH 3/6] " Christoph Egger
2010-07-27 12:18                     ` [PATCH 4/6] " Christoph Egger
2010-07-27 12:20                       ` [PATCH 5/6] " Christoph Egger
2010-07-27 12:21                         ` [PATCH 6/6] " Christoph Egger
2010-07-27 17:00                         ` [PATCH 5/6] " Ian Jackson
2010-07-28  9:17                           ` Christoph Egger
2010-07-27 16:58                       ` [PATCH 4/6] " Ian Jackson
2010-07-28 11:50                         ` Christoph Egger
     [not found]                     ` <19535.3166.214153.676101@mariner.uk.xensource.com>
2010-07-28 11:42                       ` [PATCH] libxl: compile fix Christoph Egger
2010-07-28 12:22                         ` Ian Campbell
2010-07-28 13:03                           ` Christoph Egger
2010-07-27 16:34                   ` [PATCH 2/6] libxl: portiblity fixes Ian Jackson
2010-07-28  9:06                     ` Christoph Egger [this message]
2010-07-28  9:21                       ` Keir Fraser
2010-07-28  9:30                         ` Christoph Egger
2010-07-28 11:39                     ` [PATCH] libxl: move blktap specific code into libxl_blktap.c Christoph Egger
2010-07-29 15:02                       ` Ian Jackson
2010-07-29 15:08                         ` Stefano Stabellini
2010-07-29 15:41                         ` Christoph Egger
2010-07-29 15:46                           ` Ian Jackson
2010-07-29 15:48                           ` Ian Jackson
2010-07-29 16:46                             ` [PATCH] libxl: move blktap-specific " Christoph Egger
2010-07-29 18:02                               ` Ian Jackson
2010-07-30  8:40                                 ` Christoph Egger
2010-07-30  8:45                                   ` Christoph Egger
2010-07-27 16:31                 ` [PATCH 1/6] libxl: portiblity fixes Ian Jackson
2010-07-28  9:49                   ` Christoph Egger
2010-07-27 12:17               ` [PATCH 0/6] " Christoph Egger
2010-07-27 16:30                 ` Ian Jackson

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=201007281106.01632.Christoph.Egger@amd.com \
    --to=christoph.egger@amd.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.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.