From: Boaz Harrosh <bharrosh@panasas.com>
To: open-osd mailing-list <osd-dev@open-osd.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: [PATCH 0/X] exofs patches for after 2.6.32
Date: Sun, 08 Nov 2009 12:34:44 +0200 [thread overview]
Message-ID: <4AF69EC4.70802@panasas.com> (raw)
Assorted bunch of patches to the exofs file system.
Most of these are a resend, they did not make it to 2.6.32
because the dependent bits from drivers/scsi/osd did not make
it into 2.6.32. I hope they finally will for 2.6.33.
These patches are just preliminary cleanups to some new
fixtures that will be sent next.
Thank you for reviewing
list of patches:
[PATCH 1/6] trivial: some small fixes in exofs documentation
[PATCH 2/6] exofs: More sane debug print
[PATCH 3/6] exofs: dbg-print less
[PATCH 4/6] exofs: refactor exofs_i_info initialization into common helper
[PATCH 5/6] exofs: Prints on mount and unmout
[PATCH 6/6] exofs: statfs blocks is sectors not FS blocks
Boaz
next reply other threads:[~2009-11-08 10:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 10:34 Boaz Harrosh [this message]
2009-11-08 10:36 ` [PATCH 1/6] trivial: some small fixes in exofs documentation Boaz Harrosh
2009-11-08 10:36 ` [PATCH 2/6] exofs: More sane debug print Boaz Harrosh
2009-11-08 10:37 ` [PATCH 3/6] exofs: dbg-print less Boaz Harrosh
2009-11-08 10:37 ` [PATCH 4/6] exofs: refactor exofs_i_info initialization into common helper Boaz Harrosh
2009-11-08 10:37 ` [PATCH 5/6] exofs: Prints on mount and unmout Boaz Harrosh
2009-11-08 10:38 ` [PATCH 6/6] exofs: statfs blocks is sectors not FS blocks 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=4AF69EC4.70802@panasas.com \
--to=bharrosh@panasas.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=osd-dev@open-osd.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 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.