From: Ben Greear <greearb@candelatech.com>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Comments on the bind-to-local IP patch series I posted?
Date: Thu, 24 Jan 2013 10:45:43 -0800 [thread overview]
Message-ID: <51018157.9060000@candelatech.com> (raw)
I'd really like to get some feedback on whether the patches I posted
have a chance at upstream inclusion. If the whole idea is DOA,
then just let me know and I promise not to ask again for a few
years :)
Otherwise, if any improvements are needed, I'll be happy to work on
them.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2013-01-24 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 18:45 Ben Greear [this message]
2013-01-24 19:12 ` Comments on the bind-to-local IP patch series I posted? Myklebust, Trond
2013-01-24 19:26 ` Ben Greear
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=51018157.9060000@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-nfs@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.