All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Stanislav Kinsbursky <skinsbursky@parallels.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"Trond.Myklebust@netapp.com" <Trond.Myklebust@netapp.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devel@openvz.org" <devel@openvz.org>
Subject: Re: [PATCH] NFS: hard-code init_net for NFS callback transports
Date: Wed, 13 Jun 2012 07:15:35 -0400	[thread overview]
Message-ID: <20120613111535.GA32085@fieldses.org> (raw)
In-Reply-To: <4FD84C47.8080505@parallels.com>

On Wed, Jun 13, 2012 at 12:16:07PM +0400, Stanislav Kinsbursky wrote:
> 12.06.2012 19:53, J. Bruce Fields написал:
> >On Mon, Jun 11, 2012 at 08:37:18AM -0400, J. Bruce Fields wrote:
> >>On Fri, Jun 01, 2012 at 01:55:47PM +0400, Stanislav Kinsbursky wrote:
> >>>This patch set is a bug fix for Bruce's 3.5 branch.
> >>>I'll rebase this for 3.4 and resend.
> >>
> >>Apologies for neglecting this, I'm done with the bakeathon and should be
> >>back to this soon.
> >>
> >>But, I'm a bit confused: you say you'll rebase this, but I've only seen
> >>two rebased patches for 3.4, and neither looks like a simple rebase of
> >>this one.
> >
> >Oh, I see; the backport of "SUNRPC: new svc_bind() routine introduced"
> >is a combination of the patch by the same name upstream with this one.
> >
> >In future for backports I'd rather keep a one-to-one correspondance
> >between the original patches and the backported patches.  (Even if that
> >means 4.2 might not be as "bisectable".)
> >
> >Also, get this patch into stable by just adding a "cc:
> >stable@vger.kernel.org" with the signed-off at the end of this patch.
> >
> >I've gone ahead and fixed that up; results in the "for-3.4" and
> >"for-3.5" branches of
> >
> >	git://linux-nfs.org/~bfields/linux-topics.git
> >
> >Let me know if anything looks wrong.
> >
> 
> 
> Hi, Bruce. Thanks for you time and guidance with this patch set.
> But I'm a bit confused - what I have to do now? Take the patches
> from your 3.4 branch and send them to "stable"?

No, I'll take care of them.--b.

--b.

      reply	other threads:[~2012-06-13 11:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-01  9:55 [PATCH] NFS: hard-code init_net for NFS callback transports Stanislav Kinsbursky
2012-06-11 12:37 ` J. Bruce Fields
2012-06-12 15:53   ` J. Bruce Fields
2012-06-13  8:16     ` Stanislav Kinsbursky
2012-06-13 11:15       ` 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=20120613111535.GA32085@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Trond.Myklebust@netapp.com \
    --cc=devel@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=skinsbursky@parallels.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.