From: Christoph Hellwig <hch@lst.de>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Trond Myklebust <trond.myklebust@primarydata.com>,
Linux Kernel mailing list <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [BUG] nfs3_list_one_acl oops
Date: Thu, 7 Aug 2014 09:12:24 +0200 [thread overview]
Message-ID: <20140807071224.GA17501@lst.de> (raw)
In-Reply-To: <20140806223441.GU30282@n2100.arm.linux.org.uk>
On Wed, Aug 06, 2014 at 11:34:41PM +0100, Russell King - ARM Linux wrote:
> What's happening on this? Did this get fixed for v3.16?
Trond has Andrey's patch queued up for 3.17 with a Cc to stable, so it
will go into a 3.16 stable kernel as soon as it hits Linus' tree.
WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de (Christoph Hellwig)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG] nfs3_list_one_acl oops
Date: Thu, 7 Aug 2014 09:12:24 +0200 [thread overview]
Message-ID: <20140807071224.GA17501@lst.de> (raw)
In-Reply-To: <20140806223441.GU30282@n2100.arm.linux.org.uk>
On Wed, Aug 06, 2014 at 11:34:41PM +0100, Russell King - ARM Linux wrote:
> What's happening on this? Did this get fixed for v3.16?
Trond has Andrey's patch queued up for 3.17 with a Cc to stable, so it
will go into a 3.16 stable kernel as soon as it hits Linus' tree.
next prev parent reply other threads:[~2014-08-07 7:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-26 16:21 [BUG] nfs3_list_one_acl oops Russell King - ARM Linux
2014-07-26 16:21 ` Russell King - ARM Linux
2014-07-27 13:19 ` Christoph Hellwig
2014-07-27 13:19 ` Christoph Hellwig
2014-07-27 15:15 ` Trond Myklebust
2014-07-27 15:15 ` Trond Myklebust
2014-08-06 22:34 ` Russell King - ARM Linux
2014-08-06 22:34 ` Russell King - ARM Linux
2014-08-07 7:12 ` Christoph Hellwig [this message]
2014-08-07 7:12 ` Christoph Hellwig
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=20140807071224.GA17501@lst.de \
--to=hch@lst.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=trond.myklebust@primarydata.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 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.