From: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
To: "Adamson, Dros" <Weston.Adamson@netapp.com>
Cc: linux-nfs list <linux-nfs@vger.kernel.org>
Subject: Re: SP4_MACH_CRED: v4 proc -> opcodes mapping
Date: Thu, 18 Jul 2013 20:49:31 +0000 [thread overview]
Message-ID: <1374180569.27573.0.camel@leira.trondhjem.org> (raw)
In-Reply-To: <372F77DD-8325-427B-AD09-8366DDED0A32@netapp.com>
DQpPbiBUaHUsIDIwMTMtMDctMTggYXQgMjA6NDEgKzAwMDAsIEFkYW1zb24sIERyb3Mgd3JvdGU6
DQo+IE9rLCB3aGF0IGFib3V0IFNFUVVFTkNFPyBTYW1lIHNpdHVhdGlvbiwgZXhjZXB0IHRoaXMg
dGltZSBpdCdzIGFjdHVhbGx5IGEgdjQuMSBvcC4NCg0KU0VRVUVOQ0UgaXMgc3BlY2lhbC4gSSBj
YW4ndCBzZWUgaG93IGl0IGlzIHBvc3NpYmxlIHRvIHB1dCBpdCBpbiB0aGUNCnNwb19tdXN0X2Vu
Zm9yY2UgY2F0ZWdvcnksIHNpbmNlIGl0IG5lZWRzIHRvIHByZWZpeCBhbGwgb3RoZXINCm9wZXJh
dGlvbnMuDQpJT1c6IHRoYXQgd291bGQgYXV0b21hdGljYWxseSBpbXBseSB0aGF0IHlvdSBjYW4g
b25seSB1c2UgdGhlIG1hY2hpbmUNCmNyZWRlbnRpYWwgZm9yIHRoYXQgTkZTIHNlcnZlci4NCg0K
DQotLSANClRyb25kIE15a2xlYnVzdA0KTGludXggTkZTIGNsaWVudCBtYWludGFpbmVyDQoNCk5l
dEFwcA0KVHJvbmQuTXlrbGVidXN0QG5ldGFwcC5jb20NCnd3dy5uZXRhcHAuY29tDQo=
next prev parent reply other threads:[~2013-07-18 20:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 14:46 SP4_MACH_CRED: v4 proc -> opcodes mapping Adamson, Dros
2013-07-18 14:57 ` Myklebust, Trond
2013-07-18 15:10 ` Adamson, Dros
2013-07-18 15:21 ` Myklebust, Trond
2013-07-18 15:50 ` Adamson, Dros
2013-07-18 17:08 ` Myklebust, Trond
2013-07-18 18:13 ` Adamson, Dros
2013-07-18 19:49 ` Adamson, Dros
2013-07-18 19:54 ` Myklebust, Trond
2013-07-18 20:04 ` Adamson, Dros
2013-07-18 20:06 ` Myklebust, Trond
2013-07-18 20:16 ` Adamson, Dros
2013-07-18 20:41 ` Adamson, Dros
2013-07-18 20:48 ` Myklebust, Trond
2013-07-18 20:49 ` Myklebust, Trond [this message]
2013-07-18 20:56 ` Myklebust, Trond
2013-07-18 20:36 ` Myklebust, Trond
2013-07-18 20:04 ` Should BIND_CONN_TO_SESSION be allowed to return NFS4ERR_WRONG_CRED Myklebust, Trond
2013-07-18 20:24 ` Myklebust, Trond
2013-07-19 15:09 ` [nfsv4] " J. Bruce Fields
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=1374180569.27573.0.camel@leira.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=Weston.Adamson@netapp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).