From: Jeff Garzik <jeff@garzik.org>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
Evgeniy Polyakov <zbr@ioremap.net>,
Marcin Slusarz <marcin.slusarz@gmail.com>,
Pavel Machek <pavel@suse.cz>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
open-osd <osd-dev@open-osd.org>,
Avishay Traeger <avishay@gmail.com>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 1/9] exofs: Kbuild, Headers and osd utils
Date: Wed, 01 Apr 2009 21:13:00 -0400 [thread overview]
Message-ID: <49D4111C.3010905@garzik.org> (raw)
In-Reply-To: <1238594963-9880-1-git-send-email-bharrosh@panasas.com>
Boaz Harrosh wrote:
> This patch includes osd infrastructure that will be used later by
> the file system.
>
> Also the declarations of constants, on disk structures,
> and prototypes.
>
> And the Kbuild+Kconfig files needed to build the exofs module.
>
> Signed-off-by: Boaz Harrosh <bharrosh@panasas.com>
> ---
> fs/exofs/Kbuild | 16 +++++
> fs/exofs/Kconfig | 13 ++++
> fs/exofs/common.h | 184 +++++++++++++++++++++++++++++++++++++++++++++++++++++
> fs/exofs/exofs.h | 127 ++++++++++++++++++++++++++++++++++++
> fs/exofs/osd.c | 153 ++++++++++++++++++++++++++++++++++++++++++++
> 5 files changed, 493 insertions(+), 0 deletions(-)
> create mode 100644 fs/exofs/Kbuild
> create mode 100644 fs/exofs/Kconfig
> create mode 100644 fs/exofs/common.h
> create mode 100644 fs/exofs/exofs.h
> create mode 100644 fs/exofs/osd.c
After building "osdblk", a block driver using libosd, it is my opinion
that all functions inside fs/exofs/osd.c should be moved to libosd.
I find myself copying most of that file, to use in osdblk.
Jeff
next parent reply other threads:[~2009-04-02 1:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49D374A1.5010303@panasas.com>
[not found] ` <1238594963-9880-1-git-send-email-bharrosh@panasas.com>
2009-04-02 1:13 ` Jeff Garzik [this message]
2009-04-02 7:24 ` [PATCH 1/9] exofs: Kbuild, Headers and osd utils Boaz Harrosh
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=49D4111C.3010905@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=avishay@gmail.com \
--cc=bharrosh@panasas.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=marcin.slusarz@gmail.com \
--cc=osd-dev@open-osd.org \
--cc=pavel@suse.cz \
--cc=randy.dunlap@oracle.com \
--cc=zbr@ioremap.net \
/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