From: Ben Hutchings <ben@decadent.org.uk>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: stable@vger.kernel.org, linux-nfs@vger.kernel.org,
Bryan Schumaker <bjschuma@netapp.com>
Subject: Re: [PATCH] SUNRPC: Fix a UDP transport regression
Date: Sun, 28 Oct 2012 00:33:28 +0100 [thread overview]
Message-ID: <1351380808.21585.16.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <1350925018-12926-1-git-send-email-Trond.Myklebust@netapp.com>
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
On Mon, 2012-10-22 at 12:56 -0400, Trond Myklebust wrote:
> commit f39c1bfb5a03e2d255451bff05be0d7255298fa4 and
You were too late to stop me applying the above to 3.2.30...
> commit 84e28a307e376f271505af65a7b7e212dd6f61f4 upstream.
[...]
so I had to cherry-pick this separately, with the obvious context
adjustment.
Ben.
--
Ben Hutchings
Reality is just a crutch for people who can't handle science fiction.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2012-10-27 23:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 16:56 [PATCH] SUNRPC: Fix a UDP transport regression Trond Myklebust
2012-10-27 23:33 ` Ben Hutchings [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=1351380808.21585.16.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=Trond.Myklebust@netapp.com \
--cc=bjschuma@netapp.com \
--cc=linux-nfs@vger.kernel.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 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.