From: Boaz Harrosh <bharrosh@panasas.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>,
NFS list <linux-nfs@vger.kernel.org>,
open-osd <osd-dev@open-osd.org>
Cc: Peng Tao <tao.peng@emc.com>
Subject: [PATCHSET 0/3] pnfs-obj: Fixes left-out from 3.5 for the 3.6 merge window
Date: Thu, 2 Aug 2012 15:32:41 +0300 [thread overview]
Message-ID: <501A7369.6090808@panasas.com> (raw)
Hi Trond
These fixes where for the 3.5 Kernel, Sorry I forgot about them. In any
way they should be pushed for 3.6 fixes.
(Should we pursue Stable@ for them)
This is a re-post, except the 3rd one which is a new BUG fix.
list of patches:
[PATCH 1/3] NFS41: add pg_layout_private to nfs_pageio_descriptor
[PATCH 2/3] pnfs-obj: Better IO pattern in case of unaligned offset
[PATCH 3/3] pnfs: Don't BUG on info received from Server
Thanks
Boaz
next reply other threads:[~2012-08-02 12:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 12:32 Boaz Harrosh [this message]
2012-08-02 12:34 ` [PATCH 1/3] NFS41: add pg_layout_private to nfs_pageio_descriptor Boaz Harrosh
2012-08-02 12:36 ` [PATCH 1/3 repost] " Boaz Harrosh
2012-08-02 13:06 ` Boaz Harrosh
2012-08-02 12:38 ` [PATCH 2/3] pnfs-obj: Better IO pattern in case of unaligned offset Boaz Harrosh
2012-08-02 12:40 ` [PATCH 3/3] pnfs: Don't BUG on info received from Server 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=501A7369.6090808@panasas.com \
--to=bharrosh@panasas.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=osd-dev@open-osd.org \
--cc=tao.peng@emc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox