From: "J. Bruce Fields" <bfields@fieldses.org>
To: Greg KH <greg@kroah.com>
Cc: stable@kernel.org, linux-nfs@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [stable] nfsd changes for 2.6.34
Date: Wed, 21 Apr 2010 19:41:09 -0400 [thread overview]
Message-ID: <20100421234108.GD23480@fieldses.org> (raw)
In-Reply-To: <20100421225048.GB27883@kroah.com>
On Wed, Apr 21, 2010 at 03:50:48PM -0700, Greg KH wrote:
> On Wed, Mar 31, 2010 at 03:30:29PM -0400, J. Bruce Fields wrote:
> > On Tue, Mar 30, 2010 at 01:03:20PM -0700, Greg KH wrote:
> > > Ok, care to backport them and send them to stable@kernel.org? They
> > > don't all apply cleanly from what I can see.
> >
> > Huh. I just checked out 2.6.32.10 and tried applying the patches a
> > couple different ways, and the worst I got was stuff like:
> >
> > patching file net/sunrpc/svc_xprt.c
> > Hunk #1 succeeded at 711 (offset 5 lines).
> >
> > Is that enough that you don't consider them clean?
> >
> > In any case, I'll follow up with patches generated against 2.6.32.10.
>
> You are right, I don't know what I did wrong, sorry. I've now queued
> all of these up for the next .32 tree, as they are already in
> .33-stable.
OK, thanks.--b.
prev parent reply other threads:[~2010-04-21 23:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 17:52 nfsd changes for 2.6.34 J. Bruce Fields
2010-03-24 14:24 ` J. Bruce Fields
2010-03-29 18:24 ` [stable] " Greg KH
2010-03-30 14:40 ` J. Bruce Fields
2010-03-30 20:03 ` Greg KH
2010-03-31 19:30 ` J. Bruce Fields
2010-03-31 19:47 ` [PATCH] nfsd4: don't try to map gid's in generic rpc code J. Bruce Fields
2010-04-21 22:50 ` [stable] nfsd changes for 2.6.34 Greg KH
2010-04-21 23:41 ` J. Bruce Fields [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=20100421234108.GD23480@fieldses.org \
--to=bfields@fieldses.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.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