From: Boaz Harrosh <bharrosh@panasas.com>
To: Benny Halevy <bhalevy@panasas.com>,
open-osd mailing-list <osd-dev@open-osd.org>,
pNFS Mailing List <pnfs@linux-nfs.org>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: [PATCH 0/2] libosd: Support for device lookup by osd_device_info
Date: Tue, 30 Jun 2009 20:08:10 +0300 [thread overview]
Message-ID: <4A4A467A.7020600@panasas.com> (raw)
These two patches are for Linux=2.6.32
They are for supporting what is needed by the pNFS-objects layout driver
and exofs when exporting osd(s) on the network.
Benny you will need to carry these in the pnfs tree until 2.6.32-rc1 as
prerequisite of the osd get_device_info support (will send next)
list of patches:
[PATCH 1/2] libosd: osd_dev_info: Unique Identification of an OSD device
[PATCH 2/2] libosd: osd_dev_is_ver1 - Minor API cleanup
Please review
Thanks
Boaz
next reply other threads:[~2009-06-30 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 17:08 Boaz Harrosh [this message]
2009-06-30 17:10 ` [PATCH 1/2] libosd: osd_dev_info: Unique Identification of an OSD device Boaz Harrosh
2009-06-30 17:42 ` Benny Halevy
2009-06-30 17:10 ` [PATCH 2/2] libosd: osd_dev_is_ver1 - Minor API cleanup 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=4A4A467A.7020600@panasas.com \
--to=bharrosh@panasas.com \
--cc=bhalevy@panasas.com \
--cc=linux-scsi@vger.kernel.org \
--cc=osd-dev@open-osd.org \
--cc=pnfs@linux-nfs.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