From: Greg KH <greg@kroah.com>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: stable@vger.kernel.org,
Trond Myklebust <Trond.Myklebust@netapp.com>,
open-osd <osd-dev@open-osd.org>,
NFS list <linux-nfs@vger.kernel.org>
Subject: Re: Patch Upstream: pnfs-obj: pNFS errors are communicated on iodata->pnfs_error
Date: Sun, 22 Jan 2012 14:10:21 -0700 [thread overview]
Message-ID: <20120122211021.GA3224@kroah.com> (raw)
In-Reply-To: <4F173F55.4090509@panasas.com>
On Wed, Jan 18, 2012 at 11:53:25PM +0200, Boaz Harrosh wrote:
> On 01/13/2012 01:13 AM, Greg KH wrote:
> >
> > Care to provide me such a patch for 3.0?
> >
> > thanks,
> >
> > greg k-h
>
> Hi this is a 3.1 and 3.0 version of this patch. It is based on todays
> stable tree checkout. It will apply cleanly to both linux-3.0.y and
> linux-3.1.y branches.
Thanks for the backport. As 3.1.y is now end-of-life, I've applied this
to the 3.0.y tree only.
thanks,
greg k-h
prev parent reply other threads:[~2012-01-23 0:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120111154700.61EA4262C@git.kroah.org>
[not found] ` <20120112231355.GA20151@kroah.com>
2012-01-18 21:53 ` Patch Upstream: pnfs-obj: pNFS errors are communicated on iodata->pnfs_error Boaz Harrosh
2012-01-22 21:10 ` Greg KH [this message]
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=20120122211021.GA3224@kroah.com \
--to=greg@kroah.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bharrosh@panasas.com \
--cc=linux-nfs@vger.kernel.org \
--cc=osd-dev@open-osd.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).