From: Greg KH <gregkh@linuxfoundation.org>
To: "J. Bruce Fields" <bfields@redhat.com>
Cc: stable@vger.kernel.org, linux-nfs@vger.kernel.org,
Stanislav Kinsbursky <skinsbursky@parallels.com>
Subject: Re: [PATCH 1/3] SUNRPC: new svc_bind() routine introduced
Date: Wed, 20 Jun 2012 11:18:35 -0700 [thread overview]
Message-ID: <20120620181835.GA8356@kroah.com> (raw)
In-Reply-To: <20120620180928.GB24777@pad.fieldses.org>
On Wed, Jun 20, 2012 at 02:09:29PM -0400, J. Bruce Fields wrote:
> On Wed, Jun 20, 2012 at 09:34:27AM -0700, Greg KH wrote:
> > On Mon, Jun 18, 2012 at 04:07:27PM -0400, J. Bruce Fields wrote:
> > > From: Stanislav Kinsbursky <skinsbursky@parallels.com>
> > >
> > > commit cd96891d48a945ca2011fbeceda73813d6286195 upstream.
> >
> > Um, no, that's not what this commit id is at all.
>
> Whoops, sorry! Should have been 9793f7c88. Upstream commits on #2 and
> #3 are correct.
>
> > Where did you get that from? I kind of don't trust this series now,
> > care to fix these up with the correct git commit ids and resend them?
>
> Sure, I'll resend once I get the "4/3" patch sorted out.
>
> (That got a form rejection--I assume it was the missing upstream commit
> ID? That's because there isn't one--3.4 requires a different fix. But
> I can point to where the bug got fixed upstream even if it isn't the
> same.)
You need to be really specific when sending a patch that is not
upstream, detailing why it isn't, and what different fix went in
upstream, if possible.
thanks,
greg k-h
next prev parent reply other threads:[~2012-06-20 18:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 20:07 3.4.z nfsd backports J. Bruce Fields
2012-06-18 20:07 ` [PATCH 1/3] SUNRPC: new svc_bind() routine introduced J. Bruce Fields
2012-06-20 16:34 ` Greg KH
2012-06-20 18:09 ` J. Bruce Fields
2012-06-20 18:18 ` Greg KH [this message]
2012-06-25 20:33 ` J. Bruce Fields
2012-06-25 20:44 ` J. Bruce Fields
2012-06-18 20:07 ` [PATCH 2/3] SUNRPC: move per-net operations from svc_destroy() J. Bruce Fields
2012-06-18 20:07 ` [PATCH 3/3] NFS: hard-code init_net for NFS callback transports J. Bruce Fields
2012-06-20 13:27 ` [PATCH 4/3] lockd: hard-code init_net in lockd case as well J. Bruce Fields
2012-06-20 14:54 ` Greg KH
2012-06-20 16:35 ` 3.4.z nfsd backports Greg KH
-- strict thread matches above, loose matches on Subject: below --
2012-04-25 13:37 [PATCH 0/3] SUNRPC: separate per-net data creation from service creation Stanislav Kinsbursky
2012-04-25 13:37 ` [PATCH 1/3] SUNRPC: new svc_bind() routine introduced Stanislav Kinsbursky
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=20120620181835.GA8356@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bfields@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=skinsbursky@parallels.com \
--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 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.