public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Alasdair G Kergon <agk@redhat.com>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] device-mapper: multipath
Date: Fri, 11 Feb 2005 17:31:43 +0000	[thread overview]
Message-ID: <20050211173143.GA11278@infradead.org> (raw)
In-Reply-To: <20050211171506.GX10195@agk.surrey.redhat.com>

> +#include "dm.h"
> +#include "dm-path-selector.h"
> +#include "dm-bio-list.h"
> +#include "dm-bio-record.h"
> +
> +#include <linux/ctype.h>
> +#include <linux/init.h>
> +#include <linux/mempool.h>
> +#include <linux/module.h>
> +#include <linux/pagemap.h>
> +#include <linux/slab.h>
> +#include <linux/time.h>
> +#include <linux/workqueue.h>
> +#include <asm/atomic.h>

Always include private headers after public ones.

> +MODULE_DESCRIPTION(DM_NAME " multipath target");
> +MODULE_AUTHOR("Sistina Software <dm-devel@redhat.com>");

Isn't this Red Hat now?

> +#ifndef	DM_MPATH_H
> +#define	DM_MPATH_H
> +
> +#include <linux/device-mapper.h>

no needed, a forward-declaration for struct dm_dev is enough.

> +EXPORT_SYMBOL(dm_register_path_selector);
> +EXPORT_SYMBOL(dm_unregister_path_selector);

I though we agreed to only allow GPL'ed path selectors at OSDL?

> +#ifndef	DM_PATH_SELECTOR_H
> +#define	DM_PATH_SELECTOR_H
> +
> +#include <linux/device-mapper.h>

again, doesn't look like it's needed.


  reply	other threads:[~2005-02-11 17:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-11 17:15 [PATCH] device-mapper: multipath Alasdair G Kergon
2005-02-11 17:31 ` Christoph Hellwig [this message]
2005-02-11 21:36   ` Andrew Morton
2005-02-11 21:42     ` Christoph Hellwig
2005-02-11 22:54     ` Alasdair G Kergon
2005-02-16  7:04     ` Ingo Molnar

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=20050211173143.GA11278@infradead.org \
    --to=hch@infradead.org \
    --cc=agk@redhat.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox